User experience system for improving compliance of temperature, pressure, and humidity

ABSTRACT

A building management system (BMS) for heating, ventilation, or air conditioning (HVAC) parameters in a building. The BMS includes one or more processing circuits including one or more memory devices coupled to one or more processors. The one or more processors query a training data storage and receive training data, institute a policy with a machine learning engine and train the policy using the training data, receive temperature, pressure, and humidity (TPH) sensor data from one or more sensors, determine a fault based on the TPH sensor data, provide the TPH sensor data and the fault to the policy of the machine learning engine and output a corrective action to resolve the fault, and generate a work order for a user based on the TPH sensor data, the determined fault and the corrective action.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims benefit of and priority to U.S.Provisional Patent Application No. 62/902,338 filed Sep. 18, 2019, theentire disclosure of which is incorporated by reference herein.

BACKGROUND

The present disclosure relates to control systems in a building. Moreparticularly, the present disclosure relates to improving compliance oftemperature, pressure, and humidity in building management systems.

SUMMARY

This summary is illustrative only and is not intended to be in any waylimiting. Other aspects, inventive features, and advantages of thedevices or processes described herein will become apparent in thedetailed description set forth herein, taken in conjunction with theaccompanying figures, wherein like reference numerals refer to likeelements.

One implementation of the present disclosure is a building managementsystem (BMS) for heating, ventilation, or air conditioning (HVAC)parameters in a building. The BMS includes one or more processingcircuits including one or more memory devices coupled to one or moreprocessors. The one or more memory devices store instructions thereonthat, when executed by the one or more processors, cause the one or moreprocessors to query a training data storage and receive training data,institute a policy with a machine learning engine and train the policyusing the training data, receive temperature, pressure, and humidity(TPH) sensor data from one or more sensors, determine a fault based onthe TPH sensor data, provide the TPH sensor data and the fault to thepolicy of the machine learning engine and output a corrective action toresolve the fault, generate a work order for a user based on the TPHsensor data, the determined fault, and the corrective action, andprovide the work order to a user interface.

In some embodiments, the one or more memory devices store instructionsthereon that, when executed by the one or more processors, cause the oneor more processors to adjust HVAC building equipment based on theprovided work order.

In some embodiments, the user interface includes a first user profileand a second user profile. In some embodiments, the one or more memorydevices store instructions thereon that, when executed by the one ormore processors, cause the one or more processors to generate a firstdashboard associated with the first user profile and a second dashboardassociated with the second user profile, provide a first subset ofinformation from the work order to the first dashboard, and provide asecond subset of information from the work order to the seconddashboard.

In some embodiments, the one or more memory devices store instructionsthereon that, when executed by the one or more processors, cause the oneor more processors to update the second dashboard based on an actionentered on the first dashboard.

In some embodiments, the work order is stored within the one or morememory devices. In some embodiments, the one or more memory devicesstore instructions thereon that, when executed by the one or moreprocessors, cause the one or more processors to update the work orderfrom either the first dashboard or the second dashboard.

In some embodiments, the one or more memory devices store instructionsthereon that, when executed by the one or more processors, cause the oneor more processors to assign the work order to the second dashboard fromthe first dashboard.

In some embodiments, the BMS system further includes an applicationstructured to access one of the first user profile or the second userprofile and display the associated dashboard on a human machineinterface, the associated dashboard displaying at least one of the TPHsensor data or the work order.

In some embodiments, the human machine interface includes a mobiledevice, a wall mounted panel, a monitor, a tablet, a kiosk, an augmentedreality device, a virtual reality device, or a wearable device.

In some embodiments, the one or more memory devices store instructionsthereon that, when executed by the one or more processors, cause the oneor more processors to retrieve a fault causation template, map aplurality of operational parameters relating to an associated HVACdevice to the fault causation template, map the corrective action to thefault causation template, and provide a populated fault causationtemplate to the user interface.

In some embodiments, the one or more memory devices store instructionsthereon that, when executed by the one or more processors, cause the oneor more processors to receive a notification that the work order hasbeen completed, the notification including the determined fault and afault solution, wherein the fault solution is either the correctiveaction or a different action, and train the policy with the machinelearning engine by providing the determined fault and the fault solutionto the machine learning engine.

In some embodiments, the machine learning engine includes at least oneof a neural network, a reinforcement learning scheme, a model-basedcontrol scheme, a linear regression algorithm, a decision tree, alogistic regression algorithm, and a Naïve Bayes algorithm.

Another implementation of the present disclosure is a buildingmanagement system (BMS) for heating, ventilation, or air conditioning(HVAC) parameters in a building. The BMS includes one or more processingcircuits including one or more memory devices coupled to one or moreprocessors. The one or more memory devices store instructions thereonthat, when executed by the one or more processors, cause the one or moreprocessors to receive temperature, pressure, and humidity (TPH) sensordata from one or more sensors, generate a work order using a machinelearning engine that receives the TPH sensor data and fault informationand outputs a recommended action, receive first credentials for a firstuser and grant access to a first user profile including a firstdashboard including first information based at least in part on the TPHsensor data and the work order, receive second credentials for a seconduser and grant access to a second user profile including a seconddashboard including second information based at least in part on the TPHsensor data and the work order, and provide communication between thefirst dashboard and the second dashboard.

In some embodiments, the first dashboard displays one or morecustomizable features to satisfy a first set of preferences of the firstuser and selectively displays the first information according to a typeof the first user profile, the type of the first user profile indicatinga first amount of detail regarding the TPH sensor data and the workorder that can be provided to the first dashboard. In some embodiments,the second dashboard displays the customizable features to satisfy asecond set of preferences of the second user and selectively displaysthe second information according to a type of the second user profile,the type of the second user profile indicating a second amount of detailregarding the TPH sensor data and the work order that can be provided tothe second dashboard.

In some embodiments, the one or more memory devices store instructionsthereon that, when executed by the one or more processors, cause the oneor more processors to adjust HVAC building equipment based on the workorder.

In some embodiments, providing communication between the first dashboardand the second dashboard includes at least one of updating the seconddashboard based on an action entered on the first dashboard, updatingthe work order from either the first dashboard or the second dashboard,and assigning the work order to the second dashboard from the firstdashboard.

In another embodiment, a building management system (BMS) for heating,ventilation, or air conditioning (HVAC) parameters in a buildingincludes one or more processing circuits comprising one or more memorydevices coupled to one or more processors, the one or more memorydevices configured to store instructions thereon. When executed by theone or more processors, the instructions cause the one or moreprocessors to: receive temperature, pressure, and humidity (TPH) sensordata from one or more sensors, receive a scheduling request for abuilding room via an application dashboard, the scheduling requestincluding a reservation time, a reservation date, and requested TPHsetpoints, receive a work order including a fault code affecting theavailability of the building room, determine if the building room isunavailable based on the work order, determine a required time toachieve the requested TPH setpoints based on the scheduling request andthe work order, provide the required time and a scheduling confirmationto the application dashboard, and adjust HVAC equipment in the buildingto achieve the TPH setpoints prior to the reservation date and time.

In some embodiments, determining a required time to adjust the requestedTPH setpoints includes determining a set of preconditioning parametersto be implemented in the building room prior to the reservation date andtime and determining the required time based on at least one of a timefor preconditioning parameters to be performed and a time for TPH levelsto adjust to the TPH setpoints.

In some embodiments, the preconditioning parameters include at least oneof an ultra-violet (UV) soak system, a fumigation system, a sanitizationsystem, an air removal system, and an air filtration system.

In some embodiments, the application dashboard includes a schedulinginterface configured to receive the required time and the schedulingconfirmation, adjust the required time to achieve the requested TPHsetpoints, update at least one of the reservation time, the reservationdate, and the request for the building room, and adjust thepreconditioning parameters implemented.

In some embodiments, the one or more memory devices store instructionsthereon that, when executed by the one or more processors, cause the oneor more processors to determine that the required time to achieve therequested TPH setpoints prior to the reservation date and time creates ascheduling conflict within the BMS, update the application dashboardbased on the scheduling conflict, and provide the application dashboardwith at least one of a new reservation time and a new reservation datesuch that the HVAC equipment can be adjusted prior to the reservationdate and time.

In some embodiments, the user is one of a chief compliance officer, afacilities manager, an operating room administrator, a health careprofessional or a facilities technician.

In some embodiments, the one or more memory devices store instructionsthereon that, when executed by the one or more processors, cause the oneor more processors to receive an indication that the work order has beencompleted and updating the user interface to indicate that the workorder has been completed.

In some embodiments, generating the work order includes generating a setof data including the fault and at least one of the corrective action, atime of the fault, and a location of the fault.

In some embodiments, the one or more memory devices store instructionsthereon that, when executed by the one or more processors, cause the oneor more processors to provide assistance functionality to the userinterface, receive a request for assistance from the user interface viathe assistance functionality, and provide additional information relatedto the corrective action to the user interface.

In some embodiments, the one or more memory devices store instructionsthereon that, when executed by the one or more processors, cause the oneor more processors to provide an alert in the building in response todetermining the fault, wherein the alert includes at least one of avisual alert, an audible alert, a fault indication, and correctiveaction indication.

In some embodiments, the first dashboard or the second dashboard or bothare configured to operate within a heads up display (HUD), and provide alist of inventory parts currently available for addressing the workorder.

In some embodiments, the first dashboard or the second dashboard or bothare configured to display regulations and codes related to TPHcompliance, display information related to an interrelation of TPH ofone or more building zones in the building, and display the TPH sensordata and the work order at least in part with color-coded formatting toindicate an intensity of the work order.

In some embodiments, the first dashboard or the second dashboard or bothincludes at least one of an audio interface, a visual interface, a touchscreen interface, and a holographic interface, and a visual indicatorproximate to the first dashboard or the second dashboard or bothconfigured to indicate a compliance level of the TPH sensor data.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building with a heating, ventilation, or airconditioning (HVAC) system, according to some embodiments.

FIG. 2 is a schematic of a waterside system which can be used as part ofthe HVAC system of FIG. 1, according to some embodiments,

FIG. 3 is a diagram of an airside system, which can be used as part ofthe HVAC system of FIG. 1, according to some embodiments.

FIG. 4 is a block diagram of a building management system (BMS) whichcan be used in the building of FIG. 1, according to some embodiments.

FIG. 5A is a diagram of a BMS for optimizing building conditions basedon user input, which can be used in the building of FIG. 1, according tosome embodiments.

FIG. 5B is a diagram of a BMS for providing work orders to anapplication which can be performed by the controller of FIG. 5A,according to some embodiments.

FIG. 5C is a diagram of a BMS with alert functionality which can beperformed by the controller of FIG. 5A, according to some embodiments.

FIG. 5D is a diagram of a BMS with scheduling system integration whichcan be performed by the controller of FIG. 5A, according to someembodiments.

FIG. 6A is a diagram of an application on a user interface, which can begenerated by the server of FIG. 5A, according to some embodiments.

FIG. 6B is a diagram of an application on a user interface, which can begenerated by the server of FIG. 5A, according to some embodiments.

FIG. 7 is a flow diagram of a process for optimizing building conditionsbased on user input, which can be performed by the BMS controller ofFIG. 5A, according to some embodiments.

FIG. 8 is a flow diagram of a process for predicting solutions to issuesin an HVAC system, which can be performed by the BMS controller of FIG.5A, according to some embodiments.

FIG. 9 is a flow diagram of a process optimizing control decisions forHVAC control in a building based on machine learning, which can beperformed by the BMS controller of FIG. 5A, according to someembodiments.

FIG. 10 is a flow diagram of a process for determining fault causes in aBMS, which can be performed by the BMS controller of FIG. 5A, accordingto some embodiments.

FIG. 11 is a flow diagram of a process for operating an HVAC systembased on scheduling requests, which can be performed by the BMScontroller of FIG. 5A, according to some embodiments.

DETAILED DESCRIPTION Overview

Before turning to the FIGURES, which illustrate certain exemplaryembodiments in detail, it should be understood that the presentdisclosure is not limited to the details or methodology set forth in thedescription or illustrated in the FIGURES. It should also be understoodthat the terminology used herein is for the purpose of description onlyand should not be regarded as limiting.

Referring generally to the FIGURES, systems and methods are disclosedthat improve comfortability for building occupants while maintainingappropriate levels of temperature, pressure, and humidity. In someembodiments, hospitals and/or clinics may need to conform to certaindesign criteria (e.g., American Society of Heating, Refrigerating andAir-Conditioning Engineers (ASHRAE) standard 170-2017, etc.) withregards to their HVAC systems to minimize infection, maintain staffcomfort and contribute to an environment of patient care. These designcriteria may require one or more building zones of the hospital orclinic to maintain temperature, pressure, and humidity (TPH) within acertain range or ranges. There exists a need to maintain TPH withinthese ranges while simultaneous providing comfortability to the buildingoccupants, energy efficiency, and optimization in the HVAC system.

ASHRAE Standards Overview

Rooms in hospitals may require special design considerations due tointensified infection concerns (e.g., the spread of a contagiousdisease, etc.), high air change rates, special equipment, uniqueprocedures, high internal loads and the presence of immunocompromisedpatients. However, these special considerations may be particularlyimportant for hospital operating rooms (ORs), where their purpose is tominimize infection, maintain staff comfort and contribute to anenvironment of patient care.

In some embodiments, ANSI/ASHRAE/ASHE Standard 170, Ventilation ofHealth Care Facilities, is considered a critical standard of heating,ventilation, and air conditioning (HVAC) health-care ventilation design.The intent of the standard may be to provide comprehensive guidance,including a set of minimum requirements that define ventilation systemdesign that helps provide environmental control for comfort, asepsis,and odor in health-care facilities. In some embodiments, it is adoptedby code-enforcing agencies.

The standard may define minimum design requirements only, and due to thewide diversity of patient population and variations in theirvulnerability and sensitivity, these standards may not guarantee an ORenvironment that will sufficiently provide comfort and control ofairborne contagions and other elements of concern. When selecting thetemperature and relative humidity combination to be incorporated intothe design, these standard minimums and the desires of the surgicalstaff may need to be taken into consideration. In some embodiments, theASHRAE HVAC Design Manual for Hospitals and Clinics discloses theinability to maintain low OR temperature as the primary complaint bysurgeons to facility engineers.

Building Management System and HVAC System Building Site

Referring now to FIG. 1, a perspective view of a building 10 is shown.Building 10 is served by a building management system (BMS). A BMS is,in general, a system of devices configured to control, monitor, andmanage equipment in or around a building or building area. A BMS caninclude, for example, a HVAC system, a security system, a lightingsystem, a fire alerting system, any other system that is capable ofmanaging building functions or devices, or any combination thereof.

The BMS that serves building 10 includes a HVAC system 100. HVAC system100 may include a plurality of HVAC devices (e.g., heaters, chillers,air handling units, pumps, fans, thermal energy storage, etc.)configured to provide heating, cooling, ventilation, or other servicesfor building 10. For example, HVAC system 100 includes a watersidesystem 120 and an airside system 130. Waterside system 120 may provide aheated or chilled fluid to an air handling unit of airside system 130.Airside system 130 may use the heated or chilled fluid to heat or coolan airflow provided to building 10. In some embodiments, watersidesystem 120 is replaced with a central energy plant such as central plant200, described with reference to FIG. 2.

Still referring to FIG. 1, HVAC system 100 includes a chiller 102, aboiler 104, and a rooftop air handling unit (AHU) 106. Waterside system120 may use boiler 104 and chiller 102 to heat or cool a working fluid(e.g., water, glycol, etc.) and may circulate the working fluid to AHU106. In embodiments, the HVAC devices of waterside system 120 may belocated in or around building 10 (as shown in FIG. 1) or at an offsitelocation such as a central plant (e.g., a chiller plant, a steam plant,a heat plant, etc.). The working fluid may be heated in boiler 104 orcooled in chiller 102, depending on whether heating or cooling isrequired in building 10. Boiler 104 may add heat to the circulatedfluid, for example, by burning a combustible material (e.g., naturalgas) or using an electric heating element. Chiller 102 may place thecirculated fluid in a heat exchange relationship with another fluid(e.g., a refrigerant) in a heat exchanger (e.g., an evaporator) toabsorb heat from the circulated fluid. The working fluid from chiller102 and/or boiler 104 may be transported to AHU 106 via piping 108.

AHU 106 may place the working fluid in a heat exchange relationship withan airflow passing through AHU 106 (e.g., via one or more stages ofcooling coils and/or heating coils). The airflow may be, for example,outside air, return air from within building 10, or a combination ofboth. AHU 106 may transfer heat between the airflow and the workingfluid to provide heating or cooling for the airflow. For example, AHU106 may include one or more fans or blowers configured to pass theairflow over or through a heat exchanger containing the working fluid.The working fluid may then return to chiller 102 or boiler 104 viapiping 110.

Airside system 130 may deliver the airflow supplied by AHU 106 (i.e.,the supply airflow) to building 10 via air supply ducts 112 and mayprovide return air from building 10 to AHU 106 via air return ducts 114.In some embodiments, airside system 130 includes multiple variable airvolume (VAV) units 116. For example, airside system 130 includes aseparate VAV unit 116 on each floor or zone of building 10. VAV units116 may include dampers or other flow control elements that can beoperated to control an amount of the supply airflow provided toindividual zones of building 10. In other embodiments, airside system130 delivers the supply airflow into one or more zones of building 10(e.g., via air supply ducts 112) without using intermediate VAV units116 or other flow control elements. AHU 106 may include sensors (e.g.,temperature sensors, pressure sensors, etc.) configured to measureattributes of the supply airflow. AHU 106 may receive input from sensorslocated within AHU 106 and/or within the building zone and may adjustthe flow rate, temperature, or other attributes of the supply airflowthrough AHU 106 to achieve setpoint conditions for the building zone.

Waterside System

Referring now to FIG. 2, a block diagram of a central plant 200 isshown, according to an exemplary embodiment. In brief overview, centralplant 200 may include types of equipment configured to serve the thermalenergy loads of a building or campus (i.e., a system of buildings). Forexample, central plant 200 may include heaters, chillers, heat recoverychillers, cooling towers, or other types of equipment configured toserve the heating and/or cooling loads of a building or campus. Centralplant 200 may consume resources from a utility (e.g., electricity,water, natural gas, etc.) to heat or cool a working fluid that iscirculated to one or more buildings or stored for later use (e.g., inthermal energy storage tanks) to provide heating or cooling for thebuildings. In embodiments, central plant 200 may supplement or replacewaterside system 120 in building 10 or may be implemented separate frombuilding 10 (e.g., at an offsite location).

Central plant 200 includes a plurality of subplants 202-212 including aheater subplant 202, a heat recovery chiller subplant 204, a chillersubplant 206, a cooling tower subplant 208, a hot thermal energy storage(TES) subplant 210, and a cold thermal energy storage (TES) subplant212. Subplants 202-212 consume resources from utilities to serve thethermal energy loads (e.g., hot water, cold water, heating, cooling,etc.) of a building or campus. For example, heater subplant 202 may beconfigured to heat water in a hot water loop 214 that circulates the hotwater between heater subplant 202 and building 10. Chiller subplant 206may be configured to chill water in a cold water loop 216 thatcirculates the cold water between chiller subplant 206 and building 10.Heat recovery chiller subplant 204 may be configured to transfer heatfrom cold water loop 216 to hot water loop 214 to provide additionalheating for the hot water and additional cooling for the cold water.Condenser water loop 218 may absorb heat from the cold water in chillersubplant 206 and reject the absorbed heat in cooling tower subplant 208or transfer the absorbed heat to hot water loop 214. Hot TES subplant210 and cold TES subplant 212 may store hot and cold thermal energy,respectively, for subsequent use.

Hot water loop 214 and cold water loop 216 may deliver the heated and/orchilled water to air handlers located on the rooftop of building 10(e.g., AHU 106) or to individual floors or zones of building 10 (e.g.,VAV units 116). The air handlers push air past heat exchangers (e.g.,heating coils or cooling coils) through which the water flows to provideheating or cooling for the air. The heated or cooled air may bedelivered to individual zones of building 10 to serve the thermal energyloads of building 10. The water then returns to subplants 202-212 toreceive further heating or cooling.

Although subplants 202-212 are shown and described as heating andcooling water for circulation to a building, it is understood that anyother type of working fluid (e.g., glycol, CO₂, etc.) may be used inplace of or in addition to water to serve the thermal energy loads. Inother embodiments, subplants 202-212 may provide heating and/or coolingdirectly to the building or campus without requiring an intermediateheat transfer fluid. These and other variations to central plant 200 arewithin the teachings of the present invention.

Each of subplants 202-212 may include a variety of equipment configuredto facilitate the functions of the subplant. For example, heatersubplant 202 includes a plurality of heating elements 220 (e.g.,boilers, electric heaters, etc.) configured to add heat to the hot waterin hot water loop 214. Heater subplant 202 is also shown to includeseveral pumps 222 and 224 configured to circulate the hot water in hotwater loop 214 and to control the flow rate of the hot water throughindividual heating elements 220. Chiller subplant 206 includes aplurality of chillers 232 configured to remove heat from the cold waterin cold water loop 216. Chiller subplant 206 is also shown to includeseveral pumps 234 and 236 configured to circulate the cold water in coldwater loop 216 and to control the flow rate of the cold water throughindividual chillers 232.

Heat recovery chiller subplant 204 includes a plurality of heat recoveryheat exchangers 226 (e.g., refrigeration circuits) configured totransfer heat from cold water loop 216 to hot water loop 214. Heatrecovery chiller subplant 204 is also shown to include several pumps 228and 230 configured to circulate the hot water and/or cold water throughheat recovery heat exchangers 226 and to control the flow rate of thewater through individual heat recovery heat exchangers 226. Coolingtower subplant 208 includes a plurality of cooling towers 238 configuredto remove heat from the condenser water in condenser water loop 218.Cooling tower subplant 208 is also shown to include several pumps 240configured to circulate the condenser water in condenser water loop 218and to control the flow rate of the condenser water through individualcooling towers 238.

Hot TES subplant 210 includes a hot TES tank 242 configured to store thehot water for later use. Hot TES subplant 210 may also include one ormore pumps or valves configured to control the flow rate of the hotwater into or out of hot TES tank 242. Cold TES subplant 212 includescold TES tanks 244 configured to store the cold water for later use.Cold TES subplant 212 may also include one or more pumps or valvesconfigured to control the flow rate of the cold water into or out ofcold TES tanks 244.

In some embodiments, one or more of the pumps in central plant 200(e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines incentral plant 200 include an isolation valve associated therewith.Isolation valves may be integrated with the pumps or positioned upstreamor downstream of the pumps to control the fluid flows in central plant200. In embodiments, central plant 200 may include more, fewer, ordifferent types of devices and/or subplants based on the particularconfiguration of central plant 200 and the types of loads served bycentral plant 200.

Airside System

Referring now to FIG. 3, a block diagram of an airside system 300 isshown, according to an example embodiment. In embodiments, airsidesystem 300 can supplement or replace airside system 130 in HVAC system100 or can be implemented separate from HVAC system 100. Whenimplemented in HVAC system 100, airside system 300 can include a subsetof the HVAC devices in HVAC system 100 (e.g., AHU 106, VAV units 116,duct 112, duct 114, fans, dampers, etc.) and can be located in or aroundbuilding 10. Airside system 300 can operate to heat or cool an airflowprovided to building 10 using a heated or chilled fluid provided bywaterside system 200.

In FIG. 3, airside system 300 includes an economizer-type air handlingunit (AHU) 302. Economizer-type AHUs vary the amount of outside air andreturn air used by the air handling unit for heating or cooling. Forexample, AHU 302 can receive return air 304 from building zone 306 viareturn air duct 308 and can deliver supply air 310 to building zone 306via supply air duct 312. In some embodiments, AHU 302 is a rooftop unitlocated on the roof of building 10 (e.g., AHU 106 as shown in FIG. 1) orotherwise positioned to receive both return air 304 and outside air 314.AHU 302 can be configured to operate exhaust air damper 316, mixingdamper 318, and outside air damper 320 to control an amount of outsideair 314 and return air 304 that combine to form supply air 310. Anyreturn air 304 that does not pass through mixing damper 318 can beexhausted from AHU 302 through exhaust damper 316 as exhaust air 322.

Each of dampers 316-320 can be operated by an actuator. For example,exhaust air damper 316 can be operated by actuator 324, mixing damper318 can be operated by actuator 326, and outside air damper 320 can beoperated by actuator 328. Actuators 324-328 can communicate with an AHUcontroller 330 via a communications link 332. Actuators 324-328 canreceive control signals from AHU controller 330 and can provide feedbacksignals to AHU controller 330. Feedback signals can include, forexample, an indication of a current actuator or damper position, anamount of torque or force exerted by the actuator, diagnosticinformation (e.g., results of diagnostic tests performed by actuators324-328), status information, commissioning information, configurationsettings, calibration data, and/or other types of information or datathat can be collected, stored, or used by actuators 324-328. AHUcontroller 330 can be an economizer controller configured to use one ormore control algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control actuators 324-328.

Still referring to FIG. 3, AHU 302 includes a cooling coil 334, aheating coil 336, and a fan 338 positioned within supply air duct 312.Fan 338 can be configured to force supply air 310 through cooling coil334 and/or heating coil 336 and provide supply air 310 to building zone306. AHU controller 330 can communicate with fan 338 via communicationslink 340 to control a flow rate of supply air 310. In some embodiments,AHU controller 330 controls an amount of heating or cooling applied tosupply air 310 by modulating a speed of fan 338.

Cooling coil 334 can receive a chilled fluid from waterside system 200(e.g., from cold water loop 216) via piping 342 and can return thechilled fluid to waterside system 200 via piping 344. Valve 346 can bepositioned along piping 342 or piping 344 to control a flow rate of thechilled fluid through cooling coil 334. In some embodiments, coolingcoil 334 includes multiple stages of cooling coils that can beindependently activated and deactivated (e.g., by AHU controller 330, byBMS controller 366, etc.) to modulate an amount of cooling applied tosupply air 310.

Heating coil 336 can receive a heated fluid from waterside system 200(e.g., from hot water loop 214) via piping 348 and can return the heatedfluid to waterside system 200 via piping 350. Valve 352 can bepositioned along piping 348 or piping 350 to control a flow rate of theheated fluid through heating coil 336. In some embodiments, heating coil336 includes multiple stages of heating coils that can be independentlyactivated and deactivated (e.g., by AHU controller 330, by BMScontroller 366, etc.) to modulate an amount of heating applied to supplyair 310.

Each of valves 346 and 352 can be controlled by an actuator. Forexample, valve 346 can be controlled by actuator 354 and valve 352 canbe controlled by actuator 356. Actuators 354-356 can communicate withAHU controller 330 via communications links 358-360. Actuators 354-356can receive control signals from AHU controller 330 and can providefeedback signals to controller 330. In some embodiments, AHU controller330 receives a measurement of the supply air temperature from atemperature sensor 362 positioned in supply air duct 312 (e.g.,downstream of cooling coil 334 and/or heating coil 336). AHU controller330 can also receive a measurement of the temperature of building zone306 from a temperature sensor 364 located in building zone 306.

In some embodiments, AHU controller 330 operates valves 346 and 352 viaactuators 354-356 to modulate an amount of heating or cooling providedto supply air 310 (e.g., to achieve a setpoint temperature for supplyair 310 or to maintain the temperature of supply air 310 within asetpoint temperature range). The positions of valves 346 and 352 affectthe amount of heating or cooling provided to supply air 310 by coolingcoil 334 or heating coil 336 and may correlate with the amount of energyconsumed to achieve a desired supply air temperature. AHU controller 330can control the temperature of supply air 310 and/or building zone 306by activating or deactivating coils 334-336, adjusting a speed of fan338, or a combination of both.

Still referring to FIG. 3, airside system 300 includes a buildingmanagement system (BMS) controller 366 and a client device 368. BMScontroller 366 can include one or more computer systems (e.g., servers,supervisory controllers, subsystem controllers, etc.) that serve assystem level controllers, application or data servers, head nodes, ormaster controllers for airside system 300, waterside system 200, HVACsystem 100, and/or other controllable systems that serve building 10.BMS controller 366 can communicate with multiple downstream buildingsystems or subsystems (e.g., HVAC system 100, a security system, alighting system, waterside system 200, etc.) via a communications link370 according to like or disparate protocols (e.g., LON, BACnet, etc.).In embodiments, AHU controller 330 and BMS controller 366 can beseparate (as shown in FIG. 3) or integrated. In an integratedimplementation, AHU controller 330 can be a software module configuredfor execution by a processor of BMS controller 366.

In some embodiments, AHU controller 330 receives information from BMScontroller 366 (e.g., commands, set points, operating boundaries, etc.)and provides information to BMS controller 366 (e.g., temperaturemeasurements, valve or actuator positions, operating statuses,diagnostics, etc.). For example, AHU controller 330 can provide BMScontroller 366 with temperature measurements from temperature sensors362 and 364, equipment on/off states, equipment operating capacities,and/or any other information that can be used by BMS controller 366 tomonitor or control a variable state or condition within building zone306.

Client device 368 can include one or more human-machine interfaces orclient interfaces (e.g., graphical user interfaces, reportinginterfaces, text-based computer interfaces, client-facing web services,web servers that provide pages to web clients, etc.) for controlling,viewing, or otherwise interacting with HVAC system 100, its subsystems,and/or devices. Client device 368 can be a computer workstation, aclient terminal, a remote or local interface, or any other type of userinterface device. Client device 368 can be a stationary terminal or amobile device. For example, client device 368 can be a desktop computer,a computer server with a user interface, a laptop computer, a tablet, asmartphone, a PDA, or any other type of mobile or non-mobile device.Client device 368 can communicate with BMS controller 366 and/or AHUcontroller 330 via communications link 372.

Building Management System

Referring now to FIG. 4, a block diagram of a building management system(BMS) 400 is shown, according to an example embodiment. BMS 400 can beimplemented in building 10 to automatically monitor and control buildingfunctions. BMS 400 includes BMS controller 366 and a plurality ofbuilding subsystems 428. Building subsystems 428 are shown to include abuilding electrical subsystem 434, an information communicationtechnology (ICT) subsystem 436, a security subsystem 438, a HVACsubsystem 440, a lighting subsystem 442, a lift/escalators subsystem432, and a fire safety subsystem 430. In embodiments, buildingsubsystems 428 can include fewer, additional, or alternative subsystems.For example, building subsystems 428 can also or alternatively include arefrigeration subsystem, an advertising or signage subsystem, a cookingsubsystem, a vending subsystem, a printer or copy service subsystem, orany other type of building subsystem that uses controllable equipmentand/or sensors to monitor or control building 10. In some embodiments,building subsystems 428 include waterside system 200 and/or airsidesystem 300, as described with reference to FIGS. 2 and 3.

Each of building subsystems 428 can include any number of devices,controllers, and connections for completing its individual functions andcontrol activities. HVAC subsystem 440 can include many of the samecomponents as HVAC system 100, as described with reference to FIGS. 1-3.For example, HVAC subsystem 440 can include a chiller, a boiler, anynumber of air handling units, economizers, field controllers,supervisory controllers, actuators, temperature sensors, and otherdevices for controlling the temperature, humidity, airflow, or othervariable conditions within building 10. Lighting subsystem 442 caninclude any number of light fixtures, ballasts, lighting sensors,dimmers, or other devices configured to controllably adjust the amountof light provided to a building space. Security subsystem 438 caninclude occupancy sensors, video surveillance cameras, digital videorecorders, video processing servers, intrusion detection devices, accesscontrol devices (e.g., card access, etc.) and servers, or othersecurity-related devices.

Still referring to FIG. 4, BMS controller 366 includes a communicationsinterface 407 and a BMS interface 409. Interface 407 can facilitatecommunications between BMS controller 366 and external applications(e.g., monitoring and reporting applications 422, enterprise controlapplications 426, remote systems and applications 444, applicationsresiding on client devices 448, etc.) for allowing user control,monitoring, and adjustment to BMS controller 366 and/or subsystems 428.Interface 407 can also facilitate communications between BMS controller366 and client devices 448. BMS interface 409 can facilitatecommunications between BMS controller 366 and building subsystems 428(e.g., HVAC, lighting security, lifts, power distribution, business,etc.).

Interfaces 407, 409 can be or include wired or wireless communicationsinterfaces (e.g., jacks, antennas, transmitters, receivers,transceivers, wire terminals, etc.) for conducting data communicationswith building subsystems 428 or other external systems or devices. Inembodiments, communications via interfaces 407, 409 can be direct (e.g.,local wired or wireless communications) or via a communications network446 (e.g., a WAN, the Internet, a cellular network, etc.). For example,interfaces 407, 409 can include an Ethernet card and port for sendingand receiving data via an Ethernet-based communications link or network.In another example, interfaces 407, 409 can include a Wi-Fi transceiverfor communicating via a wireless communications network. In anotherexample, one or both of interfaces 407, 409 can include cellular ormobile phone communications transceivers. In one embodiment,communications interface 407 is a power line communications interfaceand BMS interface 409 is an Ethernet interface. In other embodiments,both communications interface 407 and BMS interface 409 are Ethernetinterfaces or are the same Ethernet interface.

Still referring to FIG. 4, BMS controller 366 includes a processingcircuit 404 including a processor 406 and memory 408. Processing circuit404 can be communicably connected to BMS interface 409 and/orcommunications interface 407 such that processing circuit 404 and thecomponents thereof can send and receive data via interfaces 407, 409.Processor 406 can be implemented as a general purpose processor, anapplication specific integrated circuit (ASIC), one or more fieldprogrammable gate arrays (FPGAs), a group of processing components, orother suitable electronic processing components.

Memory 408 (e.g., memory, memory unit, storage device, etc.) can includeone or more devices (e.g., RAM, ROM, Flash memory, hard disk storage,etc.) for storing data and/or computer code for completing orfacilitating the processes, layers and modules described in the presentapplication. Memory 408 can be or include volatile memory ornon-volatile memory. Memory 408 can include database components, objectcode components, script components, or any other type of informationstructure for supporting the activities and information structuresdescribed in the present application. According to an exampleembodiment, memory 408 is communicably connected to processor 406 viaprocessing circuit 404 and includes computer code for executing (e.g.,by processing circuit 404 and/or processor 406) one or more processesdescribed herein.

In some embodiments, BMS controller 366 is implemented within a singlecomputer (e.g., one server, one housing, etc.). In other embodiments BMScontroller 366 can be distributed across multiple servers or computers(e.g., that can exist in distributed locations). Further, while FIG. 4shows applications 422 and 426 as existing outside of BMS controller366, in some embodiments, applications 422 and 426 can be hosted withinBMS controller 366 (e.g., within memory 408).

Still referring to FIG. 4, memory 408 includes an enterprise integrationlayer 410, an automated measurement and validation (AM&V) layer 412, ademand response (DR) layer 414, a fault detection and diagnostics (FDD)layer 416, an integrated control layer 418, and a building subsystemintegration later 420. Layers 410-420 can be configured to receiveinputs from building subsystems 428 and other data sources, determineoptimal control actions for building subsystems 428 based on the inputs,generate control signals based on the optimal control actions, andprovide the generated control signals to building subsystems 428. Thefollowing paragraphs describe some of the general functions performed byeach of layers 410-420 in BMS 400.

Enterprise integration layer 410 can be configured to serve clients orlocal applications with information and services to support a variety ofenterprise-level applications. For example, enterprise controlapplications 426 can be configured to provide subsystem-spanning controlto a graphical user interface (GUI) or to any number of enterprise-levelbusiness applications (e.g., accounting systems, user identificationsystems, etc.). Enterprise control applications 426 can also oralternatively be configured to provide configuration GUIs forconfiguring BMS controller 366. In yet other embodiments, enterprisecontrol applications 426 can work with layers 410-420 to optimizebuilding performance (e.g., efficiency, energy use, comfort, or safety)based on inputs received at interface 407 and/or BMS interface 409.

Building subsystem integration layer 420 can be configured to managecommunications between BMS controller 366 and building subsystems 428.For example, building subsystem integration layer 420 can receive sensordata and input signals from building subsystems 428 and provide outputdata and control signals to building subsystems 428. Building subsystemintegration layer 420 can also be configured to manage communicationsbetween building subsystems 428. Building subsystem integration layer420 translate communications (e.g., sensor data, input signals, outputsignals, etc.) across a plurality of multi-vendor/multi-protocolsystems.

Demand response layer 414 can be configured to optimize resource usage(e.g., electricity use, natural gas use, water use, etc.) and/or themonetary cost of such resource usage in response to satisfy the demandof building 10. The optimization can be based on time-of-use prices,curtailment signals, energy availability, or other data received fromutility providers, distributed energy generation systems 424, fromenergy storage 427 (e.g., hot TES 242, cold TES 244, etc.), or fromother sources. Demand response layer 414 can receive inputs from otherlayers of BMS controller 366 (e.g., building subsystem integration layer420, integrated control layer 418, etc.). The inputs received from otherlayers can include environmental or sensor inputs such as temperature,carbon dioxide levels, relative humidity levels, air quality sensoroutputs, occupancy sensor outputs, room schedules, and the like. Theinputs can also include inputs such as electrical use (e.g., expressedin kWh), thermal load measurements, pricing information, projectedpricing, smoothed pricing, curtailment signals from utilities, and thelike.

According to an example embodiment, demand response layer 414 includescontrol logic for responding to the data and signals it receives. Theseresponses can include communicating with the control algorithms inintegrated control layer 418, changing control strategies, changing setpoints, or activating/deactivating building equipment or subsystems in acontrolled manner. Demand response layer 414 can also include controllogic configured to determine when to utilize stored energy. Forexample, demand response layer 414 can determine to begin using energyfrom energy storage 427 just prior to the beginning of a peak use hour.

In some embodiments, demand response layer 414 includes a control moduleconfigured to actively initiate control actions (e.g., automaticallychanging set points) which minimize energy costs based on one or moreinputs representative of or based on demand (e.g., price, a curtailmentsignal, a demand level, etc.). In some embodiments, demand responselayer 414 uses equipment models to determine an optimal set of controlactions. The equipment models can include, for example, thermodynamicmodels describing the inputs, outputs, and/or functions performed bysets of building equipment. Equipment models can represent collectionsof building equipment (e.g., subplants, chiller arrays, etc.) orindividual devices (e.g., individual chillers, heaters, pumps, etc.).

Demand response layer 414 can further include or draw upon one or moredemand response policy definitions (e.g., databases, XML files, etc.).The policy definitions can be edited or adjusted by a user (e.g., via agraphical user interface) so that the control actions initiated inresponse to demand inputs can be tailored for the user's application,desired comfort level, particular building equipment, or based on otherconcerns. For example, the demand response policy definitions canspecify which equipment can be turned on or off in response toparticular demand inputs, how long a system or piece of equipment shouldbe turned off, what set points can be changed, what the allowable setpoint adjustment range is, how long to hold a high demand setpointbefore returning to a normally scheduled setpoint, how close to approachcapacity limits, which equipment modes to utilize, the energy transferrates (e.g., the maximum rate, an alarm rate, other rate boundaryinformation, etc.) into and out of energy storage devices (e.g., thermalstorage tanks, battery banks, etc.), and when to dispatch on-sitegeneration of energy (e.g., via fuel cells, a motor generator set,etc.).

Integrated control layer 418 can be configured to use the data input oroutput of building subsystem integration layer 420 and/or demandresponse later 414 to make control decisions. Due to the subsystemintegration provided by building subsystem integration layer 420,integrated control layer 418 can integrate control activities of thesubsystems 428 such that the subsystems 428 behave as a singleintegrated supersystem. In an example embodiment, integrated controllayer 418 includes control logic that uses inputs and outputs from aplurality of building subsystems to provide greater comfort and energysavings relative to the comfort and energy savings that separatesubsystems could provide alone. For example, integrated control layer418 can be configured to use an input from a first subsystem to make anenergy-saving control decision for a second subsystem. Results of thesedecisions can be communicated back to building subsystem integrationlayer 420.

Integrated control layer 418 is shown to be logically below demandresponse layer 414. Integrated control layer 418 can be configured toenhance the effectiveness of demand response layer 414 by enablingbuilding subsystems 428 and their respective control loops to becontrolled in coordination with demand response layer 414. Thisconfiguration may advantageously reduce disruptive demand responsebehavior relative to conventional systems. For example, integratedcontrol layer 418 can be configured to assure that a demandresponse-driven upward adjustment to the setpoint for chilled watertemperature (or another component that directly or indirectly affectstemperature) does not result in an increase in fan energy (or otherenergy used to cool a space) that would result in greater total buildingenergy use than was saved at the chiller.

Integrated control layer 418 can be configured to provide feedback todemand response layer 414 so that demand response layer 414 checks thatconstraints (e.g., temperature, lighting levels, etc.) are properlymaintained even while demanded load shedding is in progress. Theconstraints can also include setpoint or sensed boundaries relating tosafety, equipment operating limits and performance, comfort, fire codes,electrical codes, energy codes, and the like. Integrated control layer418 is also logically below fault detection and diagnostics layer 416and automated measurement and validation layer 412. Integrated controllayer 418 can be configured to provide calculated inputs (e.g.,aggregations) to these higher levels based on outputs from more than onebuilding subsystem.

Automated measurement and validation (AM&V) layer 412 can be configuredto verify that control strategies commanded by integrated control layer418 or demand response layer 414 are working properly (e.g., using dataaggregated by AM&V layer 412, integrated control layer 418, buildingsubsystem integration layer 420, FDD layer 416, or otherwise). Thecalculations made by AM&V layer 412 can be based on building systemenergy models and/or equipment models for individual BMS devices orsubsystems. For example, AM&V layer 412 can compare a model-predictedoutput with an actual output from building subsystems 428 to determinean accuracy of the model.

Fault detection and diagnostics (FDD) layer 416 can be configured toprovide on-going fault detection for building subsystems 428, buildingsubsystem devices (i.e., building equipment), and control algorithmsused by demand response layer 414 and integrated control layer 418. FDDlayer 416 can receive data inputs from integrated control layer 418,directly from one or more building subsystems or devices, or fromanother data source. FDD layer 416 can automatically diagnose andrespond to detected faults. The responses to detected or diagnosedfaults can include providing an alert message to a user, a maintenancescheduling system, or a control algorithm configured to attempt torepair the fault or to work-around the fault.

FDD layer 416 can be configured to output a specific identification ofthe faulty component or cause of the fault (e.g., loose damper linkage)using detailed subsystem inputs available at building subsystemintegration layer 420. In other example embodiments, FDD layer 416 isconfigured to provide “fault” events to integrated control layer 418which executes control strategies and policies in response to thereceived fault events. According to an example embodiment, FDD layer 416(or a policy executed by an integrated control engine or business rulesengine) can shut-down systems or direct control activities around faultydevices or systems to reduce energy waste, extend equipment life, orassure proper control response.

FDD layer 416 can be configured to store or access a variety ofdifferent system data stores (or data points for live data). FDD layer416 can use some content of the data stores to identify faults at theequipment level (e.g., specific chiller, specific AHU, specific terminalunit, etc.) and other content to identify faults at component orsubsystem levels. For example, building subsystems 428 can generatetemporal (i.e., time-series) data indicating the performance of BMS 400and the components thereof. The data generated by building subsystems428 can include measured or calculated values that exhibit statisticalcharacteristics and provide information about how the correspondingsystem or process (e.g., a temperature control process, a flow controlprocess, etc.) is performing in terms of error from its setpoint. Theseprocesses can be examined by FDD layer 416 to expose when the systembegins to degrade in performance and alert a user to repair the faultbefore it becomes more severe.

Temperature, Pressure, and Humidity System

As shown in FIG. 5A, a system 500 for controlling TPH is structured toreceive user input regarding HVAC systems (e.g., the waterside system200, the airside system 300, the BMS system 400, etc.) within thebuilding 10, and adjust control based on the user input. The system 500may include any combination of aspects described herein. For example,the HVAC equipment 524, as described below, may include the pumps 234and the fan 338, described reference to FIGS. 2 and 3 or othercomponents, as desired. The system 500 includes a BMS controller 502,the HVAC equipment 524, a building zone 526, a network 530, anapplication 532, a server 534, and user devices 536-540.

In some embodiments, the BMS controller 502 may be similar to BMScontroller 366 as described above with reference to FIG. 4. In someembodiments, BMS controller 502 incorporates additional features orfunctionality that allow for improved TPH control. The BMS controller502 includes a processing circuit 504 communicably connected to acommunications interface 522 so that the processing circuit 504 can sendand receive data via the communications interface 522. The processingcircuit 504 includes a processor 506 and a memory 508.

The processor 506 can be implemented as a general purpose processor, anapplication specific integrated circuit (ASIC), one or more fieldprogrammable gate arrays (FPGAs), a group of processing components, orother suitable electronic processing components. The memory 508 (e.g.,memory, memory unit, storage device, etc.) can include one or moredevices (e.g., RAM, ROM, Flash memory, hard disk storage, etc.) forstoring data and/or computer code for completing or facilitating theprocesses, layers and modules described in the present application.Memory 508 can be or include volatile memory or non-volatile memory. Thememory 508 can include database components, object code components,script components, or any other type of information structure forsupporting the activities and information structures described in thepresent application. According to an example embodiment, the memory 508is communicably connected to the processor 506 via the processingcircuit 504 and includes computer code for executing (e.g., by theprocessing circuit 504 and/or the processor 506) one or more processesdescribed herein.

In some embodiments, the BMS controller 502 is implemented within asingle computer (e.g., one server, one housing, etc.). In someembodiments, the BMS controller 502 is distributed across multipleservers or computers (e.g., that can exist in geographically separatedlocations). The memory 508 includes a training data storage 510, amachine learning engine 512, a fault detector circuit 514, a work ordercircuit 516, a data collector 518, and a profile database 520. While thesystems and methods disclosed herein generally refer to building controlwithin hospitals and clinics, other types of buildings, campuses, andfloorplans may implement the systems and methods disclosed herein,including data centers, fish hatcheries, pharmaceutical labs, and officebuildings. Additionally, while the BMS controller 502 is shown to handleprocessing related to collecting data, storing profile databases,artificial intelligence, etc., some or all of this functionality may beperformed in a distributed group of processors, memories, etc., orwithin cloud processed applications (e.g., the application 532).

The training data storage 510 may be configured to store data used fortraining one or more machine learning components within the system 500.For example, the training data storage 510 is shown providing trainingdata to the machine learning engine 512. In some embodiments, trainingdata includes previous fault data related to the system 500 allowing themachine learning engine 512 to develop intelligence that predictssolutions to faults in HVAC systems. For example, the training datastorage 510 may include hundreds of previous faults (e.g., stuckdampers, failed pumps, overheating boilers, stuck valves, incorrectinstallations, etc.) from HVAC equipment 524. In some embodiments, thetraining data storage 510 includes a remote database that can be queriedby the BMS controller 502 to receive the training data or a portion ofthe training data. In some embodiments, the training data storage 510 islocated locally within the BMS 502 and stores a local set of trainingdata.

The machine learning engine 512 is structured to receive the trainingdata from the training data storage 510 and determine trends in whichsolutions were implemented for correlated faults. For example,restarting a controller/actuator assembly in response to a stuck damperfault. Upon developing the intelligence for predicting solutions forparticular faults, the BMS controller 502 may then be able to providethe application 532 with a recommended solution to a fault. The faultsolution functionality described herein may be similar to faultprediction systems and methods described in U.S. Patent PublicationApplication No. 2019/0041882 filed Aug. 3, 2017, the entire disclosureof which is incorporated by reference herein.

In some embodiments, the training data includes previous fault datarelated to the system 500 such that the machine learning engine 512 candevelop intelligence for predicting solutions to work orders in HVACsystems. Work orders may be submitted via one or more building occupants(these and other information and/or requests are submitted via theapplication 532, which is described in greater detail below) orgenerated automatically either locally by a component that recognizesservice is required, a central service prediction system, a faultdetection system, or other automated systems. The work orders mayinclude standard equipment updates such as “Pump A requires an oilchange” or “Calibrate Actuator C.” However, the work orders may alsoinclude specific requests from building occupants. For example, a nurseon a hospital floor may send a request from their user device 536 viathe application 532 to replace a lightbulb in a patient room. The BMScontroller 502 may receive the user request via the network 530 andprovide a recommended solution for the work order to a technician. Thesolution may be based on one or more previously filed work orders thatmay be similar to the current work order. In the above example, thissolution may be “Replace single light bulb in Room A5—GE U-BendFluorescent Bulb (T8/Medium).” The inclusion of the recommended solutionwithin the work order facilitates a quicker completion time of the workorders.

In some embodiments, the machine learning engine 512 utilizes decisiontrees, generated models via a model predictive architecture, trendanalyses, neural networks, deep neural networks, reinforcement learning,and other machine learning and artificial intelligence schemes thatimprove over time and improve predictions of the BMS controller 502. Nomatter the specific implementation of the machine learning engine 512,the training data is utilized to develop a machine learning schemestructured to receive inputs in the form of faults or work requests, andprovide a recommended solution. As described herein, users may refer tofacility managers, technicians, nurse managers, compliance officers,nurses, doctors, and other building occupants.

The fault detector circuit 514 is structured to determine that a faulthas occurred in a system of component. In some embodiments, the fault isa sensed failure of a system or component, a manually entered fault of asystem or component, or a user request (e.g., the lightbulb exampledescribed above). The fault detector circuit 514 is structured toprovide the fault to the machine learning engine 512, and to receive arecommended solution from the machine learning engine 512. The faultdetector circuit 514 then sends the fault and the recommended solutionto the work order circuit 516. For example, the fault detector circuit514 may send the fault and recommended solution to the interface of auser device 536 via the application 532.

The work order circuit 516 is structured to receive the fault andrecommended solution from the fault detector circuit 514 and assemble awork order for distribution to relevant users via the network 530 andthe application 532. In some embodiments, the work order circuit 516assigns a priority to the generated work order based on the urgency ofthe work order. For example, a light bulb change has a significantlylower priority than a work order directed to a chiller fault that maymaterially affect TPH in a critical area.

The data collector 518 receives user requests for work orders, userrequests for information, sensor data, queried database information, andother information via the communications interface 522. In the eventthat a user requests information (e.g., TPH data for March, 2020 forbuilding zone A, etc.), data collector 518 may query a database for therequested information and provide the information to the user via theapplication 532.

The profile database 520 stores profiles of users of the application532. For example, if the application 532 is implemented for employees ofa hospital, the users may include nurses, service technicians,maintenance workers, administrators, doctors, facility managers,utilities managers, etc. may have access to the application 532. In someembodiments, each individual provided access to the application 532 isassigned a profile defining what information is available to theindividual user. In some embodiments, each user profile defines adashboard designed to provide information relevant to the user's role.For example, nurses may not need to see predicted fault solutions forfaults being detected in a chiller bank. The nurse in this example mayaccess a dashboard that provides available scheduling informationrelated to TPH and room availability, real time monitors of assignedrooms TPH, etc. The profiles generated for each user (e.g., employee,building occupant, etc.) may be stored in a separate database (e.g.,server 534) or within the BMS controller 502. The profiles may begenerated for the users upon registration in the application 532.

In some embodiments, the profile database 520 allows users to adjustpreferences within the assigned profile. For example, displayed TPHparameters and/or other parameters in building zone 526 may be adjustedby the user. A doctor may prefer a cold and dry environment duringsurgery and may enter the preferences within their assigned profile. Assuch, the OR room in which the doctor is performing surgery is set totheir preferred TPH levels, per a request sent via the application 532.The BMS controller 502 may maintain TPH levels within the OR accordingto compliant ranges, while making a best effort to satisfy the doctor'spreferences. The above example shows how the BMS controller 502maintains compliance that is required per building code (e.g., ASHRAEstandard 170, etc.) while also providing custom HVAC control andcomfortability to users.

The communications interface 522 can facilitate communications betweenthe BMS controller 502 and external systems (e.g., the application 532,the HVAC equipment 524, the monitoring and reporting applications 422,the enterprise control applications 426, the remote systems andapplications 444, the applications residing on client devices 448, etc.)for allowing user control, monitoring, and adjustment to the BMScontroller 502. The communications interface 522 can also facilitatecommunications between the BMS controller 502 and the client devices448. The communications interface 522 may facilitate communicationsbetween the BMS controller 502 and the building subsystems 428 (e.g.,the HVAC, the lighting security, the lifts, the power distribution, thebusiness, etc.). The communications interface 522 may be configured tofacilitate communication between components within the system 500,including the network 530, the HVAC sensors 528, the HVAC equipment 524,the server 534, and the user devices 536-540.

The communications interface 522 can be or include wired or wirelesscommunications interfaces (e.g., jacks, antennas, transmitters,receivers, transceivers, wire terminals, etc.) for conducting datacommunications with the application 532 or other external systems ordevices. In embodiments, communications via the communications interface522 can be direct (e.g., local wired or wireless communications) or viaa communications network such as the network 530 (e.g., a WAN, theInternet, a cellular network, etc.). For example, the communicationsinterface 522 can include an Ethernet card and port for sending andreceiving data via an Ethernet-based communications link or network. Inanother example, the communications interface 522 can include a Wi-Fitransceiver for communicating via a wireless communications network. Inanother example, the communications interface 522 can include cellularor mobile phone communications transceivers. In one embodiment, thecommunications interface 522 is a power line communication. In otherembodiments, the communications interface 522 is an Ethernet interface.

The building zone 526 may be configured to represent a region withinbuilding 10, including floors, spaces, zones, rooms, hallways, areas,and any other location within building 10. In one embodiment, thebuilding zone 526 is an operating room (OR) in a hospital. In anotherexample, the building zone 526 is a hospital floor. In another example,the building zone 526 is a region within a building that spans one ormore floors. The building zone 526 may be known to the BMS controller502 such that information may be displayed on the application 532 thatis specific to the building zone 526. In some embodiments, the buildingzone 526 spans across several buildings, such that the building zone 526acts as a campus (e.g., a hospital campus, etc.). While only a singlebuilding zone (the building zone 526) is shown in FIG. 5A, severalbuilding zones may be monitored by the BMS controller 502. For example,the BMS controller 502 is providing TPH data to the application 532 for20 different building zones: five pertaining to OR's, five pertaining toadministrative areas, five pertaining to waiting rooms, and fivepertaining to patient rooms. The number of building zones and types ofbuilding zones are non-limiting.

The HVAC sensors 528 can be or include any number and type of buildingsensors, including temperature sensors, pressure sensors, humiditysensors, flow sensors, and positional sensors. In some embodiments, theHVAC sensors 528 include temperature, pressure, and humidity sensorsconfigured to monitor the TPH levels within the building zone 526. TheHVAC sensors 528 may be configured to transmit measurements wirelesslyor wiredly. In some embodiments, the HVAC sensors 528 are plug-n-play(PnP) sensors configured to transmit data wirelessly over a buildingautomation protocol.

The network 530 may include any combination of computational and/orrouting devices configured to move data from one computer or device toanother. The network 530 may act as a local network than employs localarea network (LAN) functionality. In other embodiments, the network 530includes campus, backbone, metropolitan, wide, cloud, and internetscope. For example, the network 530 may be connected to off-premiseservers that can implement cloud networking. This may allow theapplication 532, for example, to access an off-premise server (e.g.,server 534) to retrieve data. In other embodiments, the application 532is stored in server 534 off-premise and can be hosted on user devices536-540 due to the cloud networking functionality of the network 530.

In some embodiments, the network 530 includes building automationprotocol functionality (e.g., Building Automation and Control networks(BACnet), Modbus, etc.) such that devices within the system 500 maycommunicate with one another with previously implemented software thatallows for such. In some embodiments, the system 500 is configured tooperate under Metasys® protocols, as designed by Johnson Controls, Inc.In other embodiments, the system 500 is configured to operate underVerasys® protocols, as designed by Johnson Controls, Inc. Inembodiments, the network 530 can facilitate communication across anynumber of building automation protocols, area networks, on premisenetworks, off-premise networks, and any combination thereof.

The application 532 may include features and functionality that allowusers (e.g., via user devices 536-540) to interact with the BMScontroller 502. In some embodiments, users can place requests for workorders, view TPH data relating to the building zone 526, view faultswithin the system 500, receive suggested fault solutions, and receiveupdates related to the application 532. The application 532 may beimplemented entirely on a user device, or may merely be hosted on a userdevice and stored on a server. The application 532 may be implemented asa software as a service (SaaS), infrastructure as a service (IaaS),platform as a service (PaaS), mobile backend as a service (MBaaS), orany other cloud computing method.

The server 534 may be or include one or more servers, processingcircuits, processors, memory, or any combination thereof for storing andhosting software applications, including the application 532. The server534 may be located on premise (e.g., within building 10, on a serverwithin building 10, on a computer's memory within building 10, hostedpeer-to-peer between devices within building 10, etc.) or off-premise(e.g., via cloud computing, etc.). In some embodiments, the processesfor implementing the application 532 may be distributed across multipleservers.

User devices 536-540 may include any type of smartphone, tablet,computer, workstation (e.g., terminal, etc.), personal display device,or laptop. In some embodiments, user devices 536 host the application532 and communicate with the BMS controller 502 via the network 530.User devices 536-540, while shown to include only three devices in FIG.5A, can include more or less that three devices. For example, everyemployee may be given access and a profile for the application 532. Eachdevice used by a user to access the application 532 may be considered auser device as described herein. In some embodiments, the user devicemay be permanently installed in a physical location and an interactivepanel or kiosk. In some embodiments, a user can login into their profileusing the user device so that a single user device is usable by morethan one user.

BMS with Work Order Generation

As shown in FIG. 5B, the system 500 is structured to generate andprovide work order information to the application 532. The memory 508 ofthe processing circuit 504 includes the training data storage 510, themachine learning engine 512, the fault detector circuit 514, the workorder circuit 516, the data collector 518, the profile database 520, anda scheduling circuit 542. In some embodiments, the system 500 isconfigured to receive sensor data and, in some embodiments, userrequests, and generate a work order for a particular user of application532. The data for the work order (e.g., contents of the work order,possible solutions, etc.) may be based on the inputs, machine learningfunctionality, the user's profile, scheduling conflicts, and anycombination thereof. In some embodiments, system 500 as shown in FIG. 5Bmay be a more detailed diagram of the memory 508 as described above withreference to FIG. 5A, wherein the processing is more specificallydevoted to generating appropriate work orders for one or more users ofapplication 532. As described herein, FIGS. 5B-5D may all be considereddifferent embodiments of the memory 508 as described above withreference to FIG. 5A, wherein the memory 508 may include some or allaspects of the components described therein.

The data collector 518 may receive sensor data from the HVAC sensors528. In some embodiments, the data collector 518 may also receive userrequests that may affect the generation and/or providing of work orders(e.g., a user requests an update to a previously received work order, auser wishes to update their profile which affects the type ofinformation they receive regarding work orders, etc.). The sensor datamay include PTH data regarding the building zone 526. The data collector518 may provide the sensor data to the fault detector circuit 514 andthe application 532. In some embodiments, the data is provided to theapplication 532 such that raw PTH data may be displayed on theapplication in real-time. However, circuitry may be included in memory508 that selectively provides the sensor data to the application 532.For example, the dashboard of the application 532 for a servicetechnician is only provided the PTH data in 10 minute intervals of thePTH data, even though the PTH data is taken by the HVAC sensors 528every 5 minutes.

The fault detector circuit 514 may receive the sensor data and processthe sensor data to determine if any of the sensor data is indicative ofa fault, or anything else that would necessitate a work order in system500. For example, the fault detector circuit 514 may determine that thepressure and temperature levels of building zone 526 are out ofcompliance (e.g., outside of acceptable ranges for pressure andtemperature ranges in the buildings, etc.). Accordingly, the faultdetector circuit 514 provides a signal to work order circuit 516 tobegin the process of resolving the non-compliant issues of building zone526.

In some embodiments, the fault detector circuit 514 provides fault data(e.g., sensor data, an indication of a fault, the type of detectedfault, etc.) to the machine learning engine 512 so that the machinelearning engine 512 can determine the appropriate solution and providethat to the work order circuit 516. FIG. 5B shows the fault detectorcircuit 514 providing a work order request to work order circuit 516.

The work order circuit 516 may receive the work order request as aninput for providing a work order or a notification of a work order to auser of the application 532. The work order circuit may also receive apredicted solution of the work order from the machine learning engine512. In the above example regarding non-compliant pressure andtemperature levels in building zone 526, the machine learning engine 512may use the training data 510 to develop a neural network that can learnhow to solve non-compliant PTH issues in the building zone 526 (using AItechniques described above). The work order circuit 516 may provide theissue relating to the work order to the machine learning engine 512 (notshown) and, in response, the machine learning engine 512 provides thesolution of fixing a faulty damper in the air duct 312 (e.g., the damper320).

The work order circuit 516 may also receive profile information as aninput. As described above, different amounts or types of information canbe provided to the application 532 depending on which profile is signedin to the application 532. In some embodiments, the work order circuit516 queries the profile database 520 for profile information relating tothe multiple users of the application 532. In the above example, thework order circuit queries the profiles for a nurse, a doctor, a servicetechnician, and a facility manager. The work order circuit 516determines that merely a notice (e.g., an alert, a notification, etc.)that there is an issue with pressure and temperature levels in buildingzone 526 is provided to the nurse's and the doctor's profile of theapplication 532. The service technician (via the application 532) mayreceive significantly more information, such as all of the relevantpressure and temperature data, where building zone 526 is located, andthe predicted solution to resolving the non-compliant PTH levels in thebuilding zone 526 (predicted by the machine learning engine 512). Thefacility manager may receive more supervisory information related to theissue, such as the selected service technician who is resolving theissue of the work order, the progress of solving the issue, and thepredicted solution.

In some embodiments, the work order circuit 516 includes processing thatorganizes the predicted solutions, work order requests, and relevantdata and appropriately provides the correct information to the users ofthe application 532. This correct information may be considered the workorder. Using the above example, the nurse may log into the application532 by singing into their profile and see that there was anon-compliance issue in building zone 526 and, as such, he/she cannotreserve building zone 526 for an upcoming surgery. The servicetechnician may log into the application 532 by signing into theirprofile and see that he/she has been assigned a new work order thatneeds to be completed and that a potential solution is fixing the damper320 in the air duct 312. The facility manager may log into theapplication 532 by signing into their profile and see that he/she has awork order that has almost been completed by the service technician, andthat the service technician replaced the damper 320 to resolve the workorder. The work order circuit 516 may also receive schedulinginformation (e.g., scheduling conflicts, etc.) as an input from thescheduling circuit 542.

In some embodiments, work order information, including TPH data,reporting data, summaries regarding one or more work orders, and anyother work order information may be reported and/or provided for toother systems (e.g., external and internal) for further analytics. Forexample, TPH data for a particular week within building 10 may bereported to a compliance agency to determine whether system 500 has beenoperating within compliance.

The scheduling circuit 542 may be configured to facilitate reservationsmade by users of the application 532 and provide scheduling conflicts tothe work order circuit 516. These reservations can include locationreservations with additional PTH requirements. For example, thescheduling circuit 542 may facilitate a reservation request from a nurseto request an OR room from 3:00-5:00 PM on Thursday, and that the ORroom be substantially cold and dry, as the surgery is for a burnpatient. In some embodiments, the scheduling circuit 542 accounts forthe time required to adjust from one reservation with certain PTHsettings to another reservation with different PTH settings. Using theabove example, the scheduling circuit may receive a reservation requestto request the same OR room from 5:00 PM-7:00 PM on Thursday, and thatthe OR room be substantially hot and humid. The scheduling circuit 542may not allow this to occur, as there is not sufficient time to adjustto the new settings.

Other examples of scheduling conflicts include maintenance work (e.g.,in response to receiving a work order, etc.) in building zone 526 whilethe building zone 526 is reserved. For example, an OR room is reservedon Wednesday for an all-day surgery. There is an issue with the chillerthat supplies chilled air to the OR room. The work order generated bythe work order circuit 516 may require that a shutdown of the HVACoperation in the OR room (required to resolve the work order) cannot beperformed on Wednesday as it would interfere with the reservation. Inother embodiments, the scheduling conflict is resolved by the system 500moving the all-day surgery reservation to another date and/or location,such that the service technician can resolve the work order onWednesday.

With reference to FIG. 5B, the scheduling circuit 542 may provide anynumber and types of scheduling conflicts, such as those described above,to the work order circuit 516. The work order circuit 516 may providethe work orders, work order notification, work order progress updates,and other transmissions related to the work orders to the application532.

BMS with Alert Functionality

As shown in FIG. 5C, the system 500 is structured to provide alerts tousers of the application 532 and/or building occupants of the building10. The memory 508 includes the training data storage 510, the machinelearning engine 512, the fault detector circuit 514, the data collector518, the profile database 520, and the alert circuit 544. The processingcircuit 504 may be configured to receive sensor data and appropriatelydetect a fault and generate/provide the appropriate alerts to one ormore users of the application 532. The data collector 518 may receivesensor data from the HVAC sensors 528 and provide the sensor data to thealert circuit 544.

The alert circuit 544 may be configured to detect a problem, issue, orfault in system 500 and facilitate the appropriate corrective action.The alert circuit 544 may be similar to the work order circuit 516 asdescribed above with reference to FIG. 5B. In some embodiments, thealert circuit 544 is configured to generate an alert and provide thealert information to the work order circuit 516 to generate a new workorder (not shown). In other embodiments, the alert circuit 544 merelyprovides notifications that there is an issue occurring within system500. For example, in the event that PTH levels are out of compliance inbuilding zone 526, the alert circuit 544 may turn on a notificationlight within building zone 526 with an accompanying audio alert. In someembodiments, the notifications are provided to the application 532 in aselective manner, such that the information is selectively displayedbased on the user's profile. The alert circuit 544 may also receivepredicted corrective action from the machine learning engine 512 as aninput.

In some embodiments, the alert determined by the alert circuit 514requires corrective action for resolving the alert. For example, analert that determines that temperature levels are significantly low inbuilding zone 526 due to a boiler failure may require the correctiveaction of filling up the fuel of a boiler (e.g., heating oil, kerosene,liquid propane (LP), etc.). This is a common task associated with HVACboilers, and may be predicted as the solution to the generated alert bythe machine learning engine 512. In some embodiments, the machinelearning engine 512 is similar to the machine learning engine describedabove with reference to FIGS. 5A-B. In some embodiments, the alertcircuit 546 may take in compliance information from the compliancedatabase 546.

In some embodiments, the BMS controller 502 may receive informationrelating to compliance standards for the particular type of buildingthat building 10 is. For example, if building 10 is a hospital, building10 needs to conform to at least ASHRAE standard 170. The alert circuit544 may query the compliance database 546 to gather this information anduse the compliance information to determine whether the received sensordata is indicative of a compliance issue. In some embodiments, the alertcircuit 544 also receives profile information as an input.

As described above, different amounts or types of information can beprovided to the application 532 depending on which profile is signed into the application 532. In some embodiments, the alert circuit 544queries the profile database 520 for profile information relating to themultiple users of the application 532. This process may be similar tothe querying processes via profile database 520 as described above. Insome embodiments, the alert circuit 544 includes fault detector circuit514. The fault detector circuit 514 may act as a subset of the alertcircuit 544, as a portion of the generated alerts by the alert circuit544 are faults within system 500. In some embodiments, they are lessproblematic and only require a notification to be provided to theapplication 532. They may not require and fault detection and/or faultcorrection.

The alert circuit 544 may provide profile specific alerts to theapplication 532. In some embodiments, the alerts include notifications,suggested solutions, selective information related to the alert, safetyrecommendations, and other alert elements for providing information tothe user of the application 532. In some embodiments, this alertinformation is selectively provided based on the profile of the user, asdescribed above. The alert circuit 544 may also provide equipmentcontrol signals to HVAC equipment 524 and notification control signalsto lighting 442. While not shown in FIG. 5C, the alert circuit 544 mayalso provide signals to a sound system within building 10 to provideaudible notifications regarding the generated alert.

In some embodiments, the alert circuit 544 includes a display panelpositioned in a patient room. In some embodiments, the alert circuit 544includes a display panel positioned in a nurses station. In someembodiments, the alert circuit 544 includes an audible alert. Theaudible alert may include an indication of a problem or a solution. Insome embodiments, the alert generated by the alert circuit 544 providesinformation regarding when the temperature, pressure, and humidity willbe returned to compliance. The alert may also include a communicationsent to a predetermined distribution list. The alert may also include amessage (e.g., SMS message, email, text, push notification, etc.) sentto the user.

BMS with Scheduling System Integration

As shown in FIG. 5D, the system 500 is structured to manage schedulingrequests while attempting to maintain PTH compliance. The memory 508includes the data collector 518, the profile database 520, thescheduling circuit 542, the compliance database 546 and apreconditioning circuit 548. The processing circuit 504 may beconfigured to receive sensor data and scheduling requests, process therequests in light of compliance requirements, preconditioning parametersand scheduling conflicts, and provide information related to thescheduling back to the application 532. The data collector 518 mayreceive sensor data from HVAC sensors 528 and scheduling requests fromthe application 532.

In some embodiments, these scheduling requests include reservations toreserve a room (e.g., an OR room in a hospital, etc.). The schedulingrequests may also include requests for particular HVAC parameters,including PTH levels. For example, a doctor requests the reservation ofa room where surgery will be performed. He/she prefers a cooler, dryerenvironment and, as such, request a lower temperature and humiditypercentage during the schedule reservation time. The scheduling circuit542 may also take into consideration whether the requested PTH leveeswould remain in compliance. The data collector 518 may provide thesensor data and scheduling requests (not shown) to the schedulingcircuit 542.

The scheduling circuit 542 may receive the sensor data and thescheduling requests and determine the allowability of the request. Thescheduling circuit 542 may also receive preconditioning parameters fromthe preconditioning circuit 548. In some embodiments, thepreconditioning circuit 548 is configured to organize a schedule for anoperating room in coordination with the HVAC control of system 500.Integration of the scheduling system with the controller may allow thesystem to incorporate draw down time (e.g., the time is takes tosufficiently cool the room and stabilize TPH before a surgery) into theschedule to avoid overlap of procedures or delays in the schedule do toa room that is not ready on time.

In some embodiments, the preconditioning system 548 includes asanitization system (e.g., UV soak system, a fumigation system, etc.)that executes a preconditioning routine when desired. In someembodiments, the time for preconditioning is accounted for by thescheduling circuit 542. The preconditioning circuit 548 may determinethe various preconditioning parameters required for the reservation andprovide the parameters to the scheduling circuit 542. The schedulingcircuit 542 may also receive the compliance information from thecompliance database 546.

In some embodiments, the BMS controller 502 may receive informationrelating to compliance standards for the particular type of buildingthat building 10 is. For example, if building 10 is a hospital, building10 needs to conform to at least ASHRAE standard 170. The alert circuit544 may query the compliance database 546 to gather this information anduse the compliance information to determine whether the received sensordata is indicative of a compliance issue. In some embodiments, the alertcircuit 544 also receives profile information as an input.

The scheduling circuit 542 may also receive profile information from theprofile database 520. In some embodiments, different amounts or types ofinformation can be provided to the application 532 depending on whichprofile is signed in to the application 532. In some embodiments, thescheduling circuit 542 queries the profile database 520 for profileinformation relating to the multiple users of the application 532. Thisprocess may be similar to the querying processes via profile database520 as described above.

In an exemplary embodiment, the operating room administrator enters areservation request via the application 532. The scheduling circuit 542receives the request and populates a schedule including anypreconditioning and/or draw down required. If the preconditioning ordraw down routines will exceed the available time slot requested, analert will be provided to the application 532. Once the operation isscheduled, preconditioning and draw down requests are automaticallygenerated by the BMS controller 502 and at the scheduled time, thecontroller operates the HVAC system and the preconditioning system toprepare the room on time for the scheduled operation. The schedulingcircuit 542 may provide scheduling confirmations, time delayindications, and scheduling updates to the application 532. Thescheduling circuit 542 may also be configured to provide control signalsto HVAC equipment within building subsystems 428.

Application Dashboard

As shown in FIG. 6A, the user device 540 includes a user interface 602.The user interface 602 displays the application 532 described above. Insome embodiments, the application 532 includes display icons,interactive buttons, charts, historical data, predictions, schedules,work orders, recommended solutions, potential uses for a building zone,and other information, as desired. In some embodiments, the application532 provides a dashboard 604 or a series of display windows 604 that theuser can access to view information and/or interact with the BMScontroller 502. In one non-limiting example, the dashboard 604 includesa profile header 606, a settings widget 608, a TPH window 610, a faultwindow 612, and a selection widgets 614-618.

In some embodiments, the user interface 602 includes the dashboard 604that displays real time TPH information and other information relevantto TPH compliance. In some embodiments, the dashboard includes a displaypanel mounted in a room. The display panel can provide digital readoutsof TPH within the room. In some embodiments, the display panel includesphysical sensors (e.g., a ball-in-the-wall pressure sensor, etc.) thathospital rooms have traditionally used for quick confirmation of thereadouts displayed on the dashboard. The display panel may includedigital displays of temperature, pressure, and humidity shown asspeedometer type readouts, bar displays, or other display types. In someembodiments, the display panel shows color coded elements indicating TPHcompliance status. For example, a background may change to yellow whenTPH is approaching a compliance standard, and red when TPH is out ofcompliance.

In some embodiments, the dashboard 604 includes a computer monitor at anursing station or another central location accessible near themonitored rooms. The dashboard 604 may provide audible alerts orinstructions regarding TPH compliance when a TPH compliance problem issensed or predicted by the controller. The dashboard 604 may include auser interface that allows a user to input TPH demands (e.g., a changeof temperature) within the allowable range for TPH compliance.

In some embodiments, the dashboard 604 provides the user with availableoptions for temperature, pressure, and humidity so that compliance canbe maintained. Additionally, the dashboard 604 can include a display orindication of energy consumption and/or cost savings attributed to TPHselections. For example, a warmer room temperature in the summer maylower energy consumption thereby reducing costs associated with TPH andalso meeting compliance standards.

In some embodiments, the dashboard 604 can include a mobile device(e.g., a smartphone) structured to interact with the controller. Themobile device can include an executable program stored on anon-transitory storage medium and capable of interacting via a wirelessnetwork with the controller to display information and provide feedbackfrom the user to the controller.

In some embodiments, the dashboard 604 can include a parts inventoryaccessible by a facilities director and a technician. The partsinventory can interface with the work order system to provide a listingof relevant parts in inventory and their location within the work order.The parts inventory can save valuable time by auto-generating a list ofrequired parts and tools to address the work order.

In some embodiments, the dashboard 604 includes head-up-display (HUD)interface that can be used hands free to interact with the controller.The HUD interface may be especially useful for a technician fulfilling awork order. For example, the HUD may allow for augmented realitydisplays to aid in the completion of the work order. Instructionaldiagrams, videos, or audio recordings could be displayed via the HUDinterface while leaving the technicians hands free to complete work.

In some embodiments, the dashboard 604 includes a help function asdescribed briefly above and structured to convey TPH information andcurrent system status in addition to providing access to other helpfunctions related the TPH (e.g., TPH of a hallway or adjacent rooms).The help function may also include additional details for the facilitydirector or technician to access in depth details of a system orcomponent relevant to a work order.

In some embodiments, the dashboard 604 includes a root causedetermination system that is structured to receive input from a largenumber of rooms and areas service by the HVAC system. The root causedetermination system analyzes data from different sources to identify aroot cause of a TPH problem. For example, by comparing TPH readings inadjacent rooms, and remote rooms, service by the same HVAC system, acorrelation between problematic readings may be found and the controllermay be able to identify and common component that is causing theproblem. The root cause determination system is capable of analyzingavailable information to determine a root cause and then generating awork order to address the root cause. In some embodiment, the root causedetermination system utilizes artificial intelligence or machinelearning to better analyze and understand the HVAC system andefficiently identify the root cause.

In some embodiments, the dashboard 604 includes a compliance standardssystem that directly links with a third party system to retrieve TPHcompliance standards. For example, the dashboard can display therelevant TPH standards set by CMS for the current use of the relevantroom. In some embodiments, the dashboard 604 includes an audio interfacecapable of communicating with the user audibly. In some embodiments, thedashboard 604 includes a holographic interface capable of displaying ahologram that the user can interact with. The holographic interface canbe used for augmented reality when diagnosing a problem and/orcompleting a work order.

In some embodiments, the dashboard 604 includes a scheduling interfacein communication with the scheduling circuit 542 to allow interactionwith the schedule. Preconditioning times and draw down times may bepreprogrammed into the scheduling circuit 542 so that the entry of aspecific operation includes any TPH preparation time automatically. Insome embodiments, the dashboard 604 includes an indicator providingvisual confirmation that a draw down, or a preconditioning routine is inprogress. The scheduling circuit 542 may be integrated with a securityor other door control system to inhibit access to the operating roomduring a preconditioning routine or a draw down.

The exemplary dashboard 604 shown in FIG. 6A is assigned to Jane Doe,who is a service technician permitted to see TPH data for buildingzones, fault windows (e.g., showing work orders including faults andrecommended solutions), and other information. As discussed above, eachuser profile may be assigned a different dashboard 604 so that adifferent user with a different profile may display different, more, orless information and options. The dashboard 604 may provide generalinformation to all occupants (e.g., real time TPH information, etc.).The profile header 606 may merely act as an identifier to the specificprofile associated with the displayed dashboard 604. In someembodiments, the profile header 606 includes a drop-down navigation treeto access more features of the application 532.

The settings widget 608 may act as a selection tool for choosingdifferent settings for the application 532. In some embodiments,operational criteria may be implemented that is particularly suited foran epidemiological pandemic (e.g., COVID-19). For example, during theCOVID-19 pandemic, it may be necessary to maintain the temperature,humidity, and pressure levels within a desired range. In someembodiments, multiple types of selection rules can be considered and arenot limited to a single selection that can be turned on or off. Thesettings widget 608 may provide instructions to the BMS controller 502to maintain control based on certain criteria that are specific to thecurrent setting. For example, the BMS controller 502 may includeinstructions that, when the COVID-19 setting is set, the TPH parametersof the building zone 526 should conform to ASHRAE Standard 170. In someembodiments, the setting widget 608 can be updated universally such thatthe settings are changed without input from the user and all settingsare updated within each dashboard 604. For example, the COVID-19settings may be updated in view of new studies or new standards (e.g.,an advantageous temperature range, a particular humidity threshold, anegative pressure differential, etc.). As disclosed herein, “widget” mayrefer to any component or interactive item on an interface that a usercan interact with, including buttons, scroll devices, windows,calendars, and navigation trees.

The settings widget 608 may change depending on the location of the userdevice 540 and the user profile. For example, the setting widget 608 maybe integrated with a scheduling system and recognize that a nurse isaccessing the dashboard within an OR. The settings widget 608 thendisplays OR specific settings. In some embodiments, the settings widget608 includes a burn procedure setting that dictates an increased ambienttemperature, an orthopedics procedure setting that dictates a lowertemperature, or other settings specific to the use of the OR. In someembodiments, the dashboard 608 receives information from a schedulingsystem and determines the room use and provides a room specific setting.For example, if the room is being used for an infection disease control,the dashboard may recognize the use from the scheduling system andprovide pressure settings via the settings widget 608.

The TPH window 610 displays pressure, temperature, humiditymeasurements, and time stamps. In some embodiments, the HVAC sensors 528provide sensor data to the BMS controller 502 at consistent sample rates(e.g., every second, every 10 seconds, every minute, every hour, etc.)and the BMS controller 502 provides the time stamp associated with thelast received information. In other embodiments, the user of the userdevice 540 determines the time intervals for display. For example, anurse may not want real time display of temperature which may fluctuate.The nurse may prefer an average temperature over a five minute interval.The user profile preferences can be updated to reflect the desireddisplay mode. In some embodiments, the TPH window 610 displays theASHRAE Standard 170 TPH values. For example, the ASHRAE Standard 170 maystate that temperature measurements are maintained in a temperaturerange of 20-24° C. and humidity is maintained in a humidity range of20-60% for a particular room use.

The fault window 612 displays fault information. In some embodiments,the fault window 612 displays potential fault causations and/orsolutions that may be determined at least in part by the machinelearning engine 512 as discussed above. Fault information can include atime of the fault, a raw fault code, a location of fault, a particularcontroller that discovered the fault, a particular sensor that measuredthe parameter that the fault was based on, required tools, requiredreplacement parts, inventory of replacement parts on hand, etc.

A first selection widget 614 displays “See other zones.” A user mayselect the selection widget 614 to toggle between different zones withinbuilding 10. While not shown in FIG. 6A, another window may open thatallows the user to pick other building zones to view their respectiveinformation. For example, while zone A (currently shown in FIG. 6A) mayrefer to a first OR, and other OR rooms are accessible via the selectionwidget 614. The user may interact with the selection widget 614 toaccess information for a second OR.

A second selection widget 616 displays “Fault History.” In someembodiments, the second selection widget 616 allows a user to accessprevious fault information related to the system 500. For example, aservice technician may wish to see previous data for building zone A.

A third selection widget 618 displays “Submit a Work Order.” In someembodiments, the third selection widget 618 allows a user to submit oneor more work orders requests. For example, if a TPH issue is identified,the user can interact with the third selection widget to report anissue.

The application 532 may also include functionality to reserve certainbuilding zones and/or operating rooms to avoid cross-contamination. Forexample, if a COVID-19 patient has been held in a particular room, itmay be beneficial to wait until the room is no longer hazardous (e.g.,low risk of spreading the disease, etc.) before bringing in a patientthat does not have COVID-19. As such, reservation functionality thatincorporates “hot-desking” features may be implemented. As describedherein, hot-desk functionality may refer to determining when a desk,room, zone, or other location is no longer hazardous such thatreservations may be held at or proximate to the location. In someembodiments, this hot desk functionality may take into account the airpathways within the building zone 526. For example, if a COVID-19patient is within a patient room that is directly in an air pathway froman HVAC blower fan, the application 532 may register this and determinethat all reservable locations within the air path are no longerreservable until they are considered no longer hazardous. In someembodiments, flush functionality may be implemented that allows all ofthe air in between surgeries to be flushed from the rooms. This isdescribed in greater detail with reference to FIG. 5A-D above.

Systems and methods for incorporating air pathways into HVAC control mayutilize systems described in U.S. patent application Ser. No. 16/927,063filed Jul. 13, 2020, U.S. patent application Ser. No. 16/927,281 filedJul. 13, 2020, U.S. patent application Ser. No. 16/927,318 filed Jul.13, 2020, U.S. Provisional Patent Application No. 63/044,906 filed Jun.26, 2020, U.S. patent application Ser. No. 16/927,759 filed Jul. 13,2020, U.S. patent application Ser. No. 16/927,766 filed Jul. 13, 2020,and U.S. Provisional Patent Application No. 63/071,910 filed Aug. 28,2020, the entire disclosures of which are incorporated by referenceherein.

As shown in FIG. 6B, the user interface 602 shows another embodiment ofapplication 532 and the dashboard 604. The dashboard 604 includes apersonal schedule 620, a work order window 626, and a settings window630. In some embodiments, FIG. 6B shows more functionality and displayfeatures that can be displayed on application 604. The personal schedule620 includes schedule 622 which shows current reservations for the user.In some embodiments, the reservations are specific to the user.Dashboard 604 also includes reservation request button 624. Reservationrequest button 624 may be selected by a user to request a roomreservation, such as the reservations described above with reference toFIG. 5D.

Work order window 626 includes new work order 628. In some embodiments,the user-specific work order is provided to the application 532, asdescribed above with reference to FIG. 5B. These user-specific workorders may be displayed in work order window 626 for viewing. In someembodiments, the information relating to the work order or othernotification (e.g., alert, update, etc.) is specific to the profile ofthe user signed in to the application 532.

The dashboard 604 includes settings window 630. In some embodiments,settings window allows a user to set particular settings for thebuilding zone 526. In some embodiments, settings window 630 is used toprovide HVAC settings when making a reservation. For example, a userselections request reservation button 624 and, when prompted foradditional information, the user indicates that “Burn Patient” settingfrom the settings window 630 should be applied during the reservation.

In some embodiments, dashboard 604 includes functionality for viewing orchecking the progress of a work order. This may provide real-time statusof the completion of the work order or various checkpoints throughoutthe process. This functionality may be embedded on dashboard 604 to beselected by a user via a button or other widget. For example, a userselects a work order progress button to view the status of a pendingwork order.

TPH Control Processes

As shown in FIG. 7, a process 700 for controlling building conditionsbased on user input is performed by the BMS controller 502, or partiallyor entirely by any other processing device in the system 500. Forexample, the BMS controller 502 performs steps 702-704, and theapplication 532 performs steps 706-710.

At step 702, the process 700 receives sensor data from one or moresensors. In some embodiments, the HVAC sensors 528 can provide sensordata to the BMS controller 502 for processing. While not shown in FIG.5A, the server 534 may handle the processing of all the sensor data andthe HVAC sensors 528 provide the sensor data to the server 534 forprocessing. The BMS controller 502 may receive the sensor datawirelessly via plug-n-play functionality or wiredly, which may beperformed over BACnet protocol or other building automation protocols.

At step 704, the process 700 provides the sensor data to a userinterface. In some embodiments, the user may want to simply view the rawdata from the HVAC sensors 528 and the BMS controller 502 may simplyreceive the sensor data and provide the data to the application 532 fordisplay on the user interface 602. In some embodiments, the BMScontroller 502 may selectively provide data based on the user's request.For example, the user may not want to see all sensor data from all theHVAC sensors 528 in the building zone 526, and may only wish to see TPHinformation from a single room.

At step 706, the process 700 receives a request to adjust buildingconditions from the user device. In some embodiments, a user requests achange in building conditions via the application 532. For example, auser may want to adjust the TPH levels of an operating room in ahospital, as the surgeon prefers a cooler, more dry room. Accordingly, anurse requests (via the application 532) a TPH change. This change maybe requested digitally (e.g., the nurse can select an actual value forthe TPH parameters, etc.), or via analog (e.g., the nurse can rotate adial to adjust TPH parameters, etc.). The BMS controller 502 may receivethe request and adjust HVAC equipment 524 to satisfy the request.

At step 708, the process 700 adjusts HVAC equipment to satisfy therequest while maintaining temperature, pressure, and humidity within apredetermined range. As described above, this step may be performed bythe BMS controller 502 by sending control signals to HVAC equipment 524.In some embodiments, the BMS controller 502 takes into account andpredictions or trends analyzed by the machine learning engine 512 whenproviding control signals.

At step 710, the process 700 provides a notification to the userinterface indicating that the request has been satisfied. Theapplication 532 may display a completion notice that the TPH levels havebeen adjusted accordingly. In some embodiments, notifications to theapplication 532 may be provided for completed workers and resolvedfaults in the system 500 as well. Notifications may include textmessages, picture messages, or a combination of both. In someembodiments, the application 532 sends a text message to the user deviceusing the application 532 to notify them that their request wassatisfied.

As shown in FIG. 8, a process 800 for predicting solutions to faults inan HVAC system is performed by the BMS controller 502, or partially orentirely by any other processing device in the system 500. For example,the BMS controller 502 may perform the steps 802-810.

At step 802, the process 800 receives the work order training dataincluding previously filed work orders for the HVAC equipment andsolutions implemented to satisfy the previously filed work orders. Insome embodiments, the training data storage 510 provides the work ordertraining data to the machine learning engine 512 for processing.

At step 804, the process 800 generates a policy based on the work ordertraining data and the solutions implemented to satisfy the work orderswithin the work order training data. In some embodiments, the machinelearning engine 512 generates a policy that is initially trained, thencontinues to learn as new faults are entered and addressed over time. Insome embodiments, the machine learning engine 512 uses reinforcementlearning based on a time to address a fault, a neural network, deeplearning networks, or other machine learning architectures. The policycan include mathematical algorithms that are trained using the trainingdata perhaps human input (for verification purposes) to replicate adecision that an expert would make when provided the same information.These algorithms may be supervised or unsupervised.

At step 806, the process 800 receives a new work order from the userdevice 538. The fault detector circuit 514 provides the work order tothe machine learning engine 512 may provide an educated guess on how toresolve or complete the work order, as described in step 808. Process800 includes predicting an appropriate solution to satisfy the new workorder based on the model (Step 808).

Process 810 includes providing the new work order and the appropriatesolution to the user interface (step 810). Step 810 may include keepingthe user updated throughout the work order process. The BMS controller502 may provide a notification that the work order has been received, anotification that the work order is being completed, and a notificationthat the work order has been completed.

As shown in FIG. 9, a process 900 for controlling the HVAC control in abuilding based on machine learning is shown, according to exemplarembodiments. Process 900 may be similar to process 800 in that a machinelearning module is being implemented to make predictions on how to solveissues within the system 500. Process 900 may be performed by The BMScontroller 502, or partially or entirely by any other processing devicein the system 500. For example, The BMS controller 502 may perform stepsall steps 902-906.

At step 902, the process 900 receives training data, the training dataincluding satisfied requests and sensor data corresponding to thesatisfied requests. Step 902 may act as a more generalized embodiment ofthe processes disclosed above with reference to FIG. 8. Step 902 may beimplementing machine learning for the entire TPH control within thebuilding zone 526. As TPH management may be difficult due to thedependency between the variables: pressure, temperature, and humidity,the machine learning functionality may improve management of TPH levelsin necessary regions while maintaining user comfortability for buildingoccupants.

At step 904, the process 900 generates a model of adjustments to thetemperature, pressure, and humidity settings based on the plurality ofsatisfied requests. At step 906, the process 900 determines optimizedcontrol decisions based on the model to increase energy efficiency orcomfortability or both while still satisfying the request. This may besimilar to the machine learning described above, where training data isreceived to train a model. As described herein, machine learning mayrefer to training algorithms that model a system of data trend. Forexample, the temperature, pressure, and humidity parameters may have anonlinear relationship. Due to this, an algorithm (e.g., a neuralnetwork matrix, etc.) may be generated to attempt to understand andlearn the nonlinear relationship. One method of training the algorithmmay include separating the previous data points of the TPHmeasurements—acting as the training data—and providing them to a neuralnetwork as time series data. In this example, the neural network may bea Long Short-Term Model (LSTM), as the inputs are timeseries data. Theneural network may provide the predicted outcome of the variables basedon the historical data (e.g., the training data). A human may verify thedecisions of the neural network via supervised learning. types ofartificial intelligence, machine learning techniques, and types ofneural networks may be considered.

As shown in FIG. 10, a process 1000 determines fault causes in a BMS.Process 1000 may be performed by the BMS controller 502. Process 1000may implement machine learning to optimizing the mapping processdescribed therein.

At step 1002, the process 1000 includes detecting a fault condition inan HVAC device. In some embodiments, the HVAC device is part of the HVACequipment 524. The fault condition can include any type of fault thatwould occur in an HVAC system and/or the system 500. Common faults caninclude stuck dampers, stuck actuators, inoperable pumps, incorrecttemperatures, low operating voltages, and low pump speed. While thesystems and methods disclosed herein generally refer to a user using theapplication 532 to report information, HVAC sensors measuring parametersin the building zone 526 (or operations of HVAC equipment 524) mayautomatically provide fault indications to the BMS controller 502.

At step 1004, the process 1000 includes mapping operational data of theHVAC device to a fault template to determine a potential cause of thefault condition. In some embodiments, a fault causation template may beused that facilitates the relationship between operational data andpredicted faults to determine potential fault causations. In otherembodiments, machine learning techniques can be used (as describedabove). Other types of methods to determine solutions to resolve faultsmay also be considered, such as querying a database of previouslyresolved faults.

At step 1006, the process 1000 includes providing the detected faultcondition and potential cause of the fault condition to the userinterface. Step 1006 may include keeping the user updated throughout thefault detection and solution process. The BMS controller 502 may providea notification that the fault detection has occurred, a notificationthat the fault is in the process of being resolved, and a notificationthat the fault has been resolved. This may also include the predictedfault solution being provided to a service technician via theapplication 532.

As shown in FIG. 11, a process 1100 adjusts HVAC parameters based onreceived scheduling requests. In some embodiments, process 1100 isperformed by scheduling circuit 542. Process 1100 may be implemented todetermine the appropriate preconditioning requirements for a schedulingreservation requested by a user.

At step 1102, the process 1100 receives a scheduling request form a userinterface of an application. In some embodiments, the application 532provides a scheduling request to the data collector 518. The datacollector 518 may also receive sensor data from HVAC sensors 528. Thescheduling request may be performed by clicking reservation button 624via dashboard 604.

At step 1104, the process 1100 populates a schedule based on the requestfrom the user. The data collector 518 may provide the sensor data andrequest to the scheduling circuit 542. The scheduling circuit 542 maythen provide the appropriate updates to the schedule. In someembodiments, the preconditioning parameters related to the schedulingrequest, compliance thresholds, user's profile, and scheduling conflictsare taken into account prior to providing the scheduling updates to theapplication 532.

At step 1106, the process 1100 automatically generates preconditioningrequirements based on the request. At step 1108, the process 1100 addspreconditioning requirements to the schedule. In some embodiments,preconditioning circuit 548 determines the appropriate conditioningservices that are required prior to the reservations. These couldinclude different sanitization techniques (e.g., UV wash, disinfectingthe room, etc.), PTH changes, equipment changes, and other adjustments.The preconditioning circuit 548 may determine which of these servicesare required for the scheduling request and provide these to thescheduling circuit 542. The scheduling circuit 542 may take these intoconsideration when determining whether the request can be approved. Forexample, the schedule request is for a time in which the room isreserved up to 10 minutes before the requested reservation time and thepreconditioning services would take approximately 20 minutes tocomplete, the scheduling circuit 542 may deny the scheduling request.

At step 1110, the process 1100 operates the HVAC equipment to satisfythe preconditioning requirements for the reservation. Scheduling circuit542 may provide control signals to HVAC equipment 524 to adjust the HVACparameters to satisfy the scheduling request. In some embodiments, thescheduling circuit 542 may also provide control signals to the lightingsubsystem 442 (e.g., for a UV wash that is required prior to thereservation, etc.).

Configuration of Exemplary Embodiments

As utilized herein, the terms “approximately,” “about,” “substantially”,and similar terms are intended to have a broad meaning in harmony withthe common and accepted usage by those of ordinary skill in the art towhich the subject matter of this disclosure pertains. It should beunderstood by those of skill in the art who review this disclosure thatthese terms are intended to allow a description of certain featuresdescribed and claimed without restricting the scope of these features tothe precise numerical ranges provided. Accordingly, these terms shouldbe interpreted as indicating that insubstantial or inconsequentialmodifications or alterations of the subject matter described and claimedare considered to be within the scope of the disclosure as recited inthe appended claims.

It should be noted that the term “exemplary” and variations thereof, asused herein to describe embodiments, are intended to indicate that suchembodiments are possible examples, representations, or illustrations ofpossible embodiments (and such terms are not intended to connote thatsuch embodiments are necessarily extraordinary or superlative examples).

The term “coupled” and variations thereof, as used herein, means thejoining of two members directly or indirectly to one another. Suchjoining may be stationary (e.g., permanent or fixed) or moveable (e.g.,removable or releasable). Such joining may be achieved with the twomembers coupled directly to each other, with the two members coupled toeach other using a separate intervening member and any additionalintermediate members coupled with one another, or with the two memberscoupled to each other using an intervening member that is integrallyformed as a single unitary body with one of the two members. If“coupled” or variations thereof are modified by an additional term(e.g., directly coupled), the generic definition of “coupled” providedabove is modified by the plain language meaning of the additional term(e.g., “directly coupled” means the joining of two members without anyseparate intervening member), resulting in a narrower definition thanthe generic definition of “coupled” provided above. Such coupling may bemechanical, electrical, or fluidic.

The term “or,” as used herein, is used in its inclusive sense (and notin its exclusive sense) so that when used to connect a list of elements,the term “or” means one, some, or all of the elements in the list.Conjunctive language such as the phrase “at least one of X, Y, and Z,”unless specifically stated otherwise, is understood to convey that anelement may be either X, Y, Z; X and Y; X and Z; Y and Z; or X, Y, and Z(i.e., any combination of X, Y, and Z). Thus, such conjunctive languageis not generally intended to imply that certain embodiments require atleast one of X, at least one of Y, and at least one of Z to each bepresent, unless otherwise indicated.

References herein to the positions of elements (e.g., “top,” “bottom,”“above,” “below”) are merely used to describe the orientation ofelements in the FIGURES. It should be noted that the orientation ofelements may differ according to other exemplary embodiments, and thatsuch variations are intended to be encompassed by the presentdisclosure.

The hardware and data processing components used to implement theprocesses, operations, illustrative logics, logical blocks, modules andcircuits described in connection with the embodiments disclosed hereinmay be implemented or performed with a general purpose single- ormulti-chip processor, a digital signal processor (DSP), an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA), or other programmable logic device, discrete gate or transistorlogic, discrete hardware components, or any combination thereof designedto perform the functions described herein. A general purpose processormay be a microprocessor, or, any conventional processor, controller,microcontroller, or state machine. A processor also may be implementedas a combination of computing devices, such as a combination of a DSPand a microprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration. In some embodiments, particular processes and methods maybe performed by circuitry that is specific to a given function. Thememory (e.g., memory, memory unit, storage device) may include one ormore devices (e.g., RAM, ROM, Flash memory, hard disk storage) forstoring data and/or computer code for completing or facilitating theprocesses, layers and modules described in the present disclosure. Thememory may be or include volatile memory or non-volatile memory, and mayinclude database components, object code components, script components,or any other type of information structure for supporting the activitiesand information structures described in the present disclosure.According to an exemplary embodiment, the memory is communicablyconnected to the processor via a processing circuit and includescomputer code for executing (e.g., by the processing circuit or theprocessor) the one or more processes described herein.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing operations. Theembodiments of the present disclosure may be implemented using existingcomputer processors, or by a special purpose computer processor for anappropriate system, incorporated for this or another purpose, or by ahardwired system. Embodiments within the scope of the present disclosureinclude program products comprising machine-readable media for carryingor having machine-executable instructions or data structures storedthereon. Such machine-readable media can be any available media that canbe accessed by a general purpose or special purpose computer or othermachine with a processor. By way of example, such machine-readable mediacan comprise RAM, ROM, EPROM, EEPROM, or other optical disk storage,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to carry or store desired program code in theform of machine-executable instructions or data structures and which canbe accessed by a general purpose or special purpose computer or othermachine with a processor. Combinations of the above are also includedwithin the scope of machine-readable media. Machine-executableinstructions include, for example, instructions and data which cause ageneral purpose computer, special purpose computer, or special purposeprocessing machines to perform a certain function or group of functions.

Although the figures and description may illustrate a specific order ofmethod steps, the order of such steps may differ from what is depictedand described, unless specified differently above. Also, two or moresteps may be performed concurrently or with partial concurrence, unlessspecified differently above. Such variation may depend, for example, onthe software and hardware systems chosen and on designer choice. Allsuch variations are within the scope of the disclosure. Likewise,software implementations of the described methods could be accomplishedwith standard programming techniques with rule-based logic and otherlogic to accomplish the connection steps, processing steps, comparisonsteps, and decision steps.

It is important to note that the construction and arrangement of systems(e.g., system 100, system 200, etc.) and methods as shown in theexemplary embodiments is illustrative only. Additionally, any elementdisclosed in one embodiment may be incorporated or utilized with anyother embodiment disclosed herein. Although only one example of anelement from one embodiment that can be incorporated or utilized inanother embodiment has been described above, it should be appreciatedthat other elements of the embodiments may be incorporated or utilizedwith any of the other embodiments disclosed herein.

What is claimed is:
 1. A building management system (BMS) for heating,ventilation, or air conditioning (HVAC) parameters in a building, theBMS comprising: one or more processing circuits comprising one or morememory devices coupled to one or more processors, the one or more memorydevices configured to store instructions thereon that, when executed bythe one or more processors, cause the one or more processors to:institute a policy with a machine learning engine and train the policyusing training data, receive temperature, pressure, and humidity (TPH)sensor data from one or more sensors, determine a fault based on the TPHsensor data, provide the TPH sensor data and the fault to the policy ofthe machine learning engine and output a corrective action to resolvethe fault, and generate a work order for a user based on the TPH sensordata, the determined fault, and the corrective action, and.
 2. The BMSof claim 1, wherein the user interface includes a first user profile anda second user profile, and wherein the one or more memory devices arefurther configured to store instructions thereon that, when executed bythe one or more processors, cause the one or more processors to:generate a first dashboard associated with the first user profile and asecond dashboard associated with the second user profile, provide afirst subset of information from the work order to the first dashboard,and provide a second subset of information from the work order to thesecond dashboard.
 3. The BMS of claim 2, wherein the one or more memorydevices are further configured to store instructions thereon that, whenexecuted by the one or more processors, cause the one or more processorsto: update the second dashboard based on an action entered on the firstdashboard.
 4. The BMS of claim 2, wherein the work order is storedwithin the one or more memory devices, and wherein the one or morememory devices are further configured to store instructions thereonthat, when executed by the one or more processors, cause the one or moreprocessors to: update the work order from either the first dashboard orthe second dashboard.
 5. The BMS of claim 2, wherein the one or morememory devices are further configured to store instructions thereonthat, when executed by the one or more processors, cause the one or moreprocessors to: assign the work order to the second dashboard from thefirst dashboard.
 6. The BMS of claim 2, further comprising anapplication structured to access one of the first user profile or thesecond user profile and display the associated dashboard on a humanmachine interface, the associated dashboard displaying at least one ofthe TPH sensor data or the work order.
 7. The BMS of claim 6, whereinthe human machine interface includes a mobile device, a wall mountedpanel, a monitor, a tablet, a kiosk, an augmented reality device, avirtual reality device, or a wearable device.
 8. The BMS of claim 1,wherein the one or more memory devices are further configured to storeinstructions thereon that, when executed by the one or more processors,cause the one or more processors to: retrieve a fault causationtemplate, map a plurality of operational parameters relating to anassociated HVAC device to the fault causation template, map thecorrective action to the fault causation template, and provide apopulated fault causation template to the user interface.
 9. The BMS ofclaim 1, wherein the one or more memory devices are further configuredto store instructions thereon that, when executed by the one or moreprocessors, cause the one or more processors to: receive a notificationthat the work order has been completed, the notification comprising thedetermined fault and a fault solution, wherein the fault solution iseither the corrective action or a different action, and train the policywith the machine learning engine by providing the determined fault andthe fault solution to the machine learning engine.
 10. The BMS of claim1, wherein the machine learning engine includes at least one of a neuralnetwork, a reinforcement learning scheme, a model-based control scheme,a linear regression algorithm, a decision tree, a logistic regressionalgorithm, and a Naïve Bayes algorithm.
 11. The BMS of claim 1, whereinthe user is one of a chief compliance officer, a facilities manager, anoperating room administrator, a health care professional or a facilitiestechnician.
 12. The BMS of claim 1, wherein the one or more memorydevices are further configured to store instructions thereon that, whenexecuted by the one or more processors, cause the one or more processorsto: provide the work order to a user interface, receive an indicationthat the work order has been completed, and updating the user interfaceto indicate that the work order has been completed.
 13. The BMS of claim1, wherein the one or more memory devices are further configured tostore instructions thereon that, when executed by the one or moreprocessors, cause the one or more processors to: provide assistancefunctionality to the user interface, receive a request for assistancefrom the user interface via the assistance functionality, and provideadditional information related to the corrective action to the userinterface.
 14. The BMS of claim 1, wherein the one or more memorydevices are further configured to store instructions thereon that, whenexecuted by the one or more processors, cause the one or more processorsto: provide an alert in the building in response to determining thefault, wherein the alert includes at least one of a visual alert, anaudible alert, a fault indication, and corrective action indication. 15.A building management system (BMS) for heating, ventilation, or airconditioning (HVAC) parameters in a building, the BMS comprising: one ormore processing circuits comprising one or more memory devices coupledto one or more processors, the one or more memory devices configured tostore instructions thereon that, when executed by the one or moreprocessors, cause the one or more processors to: receive temperature,pressure, and humidity (TPH) sensor data from one or more sensors,generate a work order using a machine learning engine that receives theTPH sensor data and fault information and outputs a recommended action,receive first credentials for a first user and grant access to a firstuser profile including a first dashboard including first informationbased at least in part on the TPH sensor data and the work order,receive second credentials for a second user and grant access to asecond user profile including a second dashboard including secondinformation based at least in part on the TPH sensor data and the workorder, and provide communication between the first dashboard and thesecond dashboard.
 16. The BMS of claim 15, wherein the first dashboardis configured to: display one or more customizable features to satisfy afirst set of preferences of the first user, and selectively display thefirst information according to a type of the first user profile, thetype of the first user profile indicating a first amount of detailregarding the TPH sensor data and the work order that can be provided tothe first dashboard, and wherein the second dashboard is configured to:display the customizable features to satisfy a second set of preferencesof the second user, and selectively display the second informationaccording to a type of the second user profile, the type of the seconduser profile indicating a second amount of detail regarding the TPHsensor data and the work order that can be provided to the seconddashboard.
 17. The BMS of claim 15, wherein providing communicationbetween the first dashboard and the second dashboard comprises at leastone of: updating the second dashboard based on an action entered on thefirst dashboard, updating the work order from either the first dashboardor the second dashboard, and assigning the work order to the seconddashboard from the first dashboard.
 18. The BMS of claim 15, wherein thefirst dashboard or the second dashboard or both are configured to:operate within a heads up display (HUD), and provide a list of inventoryparts currently available for addressing the work order.
 19. The BMS ofclaim 15, wherein the first dashboard or the second dashboard or bothare configured to: display regulations and codes related to TPHcompliance, display information related to an interrelation of TPH ofone or more building zones in the building, and display the TPH sensordata and the work order at least in part with color-coded formatting toindicate an intensity of the work order.
 20. The BMS of claim 15,wherein the first dashboard or the second dashboard or both include: atleast one of an audio interface, a visual interface, a touch screeninterface, or a holographic interface, and a visual indicator proximateto the first dashboard or the second dashboard or both configured toindicate a compliance level of the TPH sensor data.